|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] enhance HVM xentrace
I've been using the VMX tracing (also modified, and with some
additional ugly shadow tracing) to analyze overhead of different
operations, as well as to look for patterns. There's some pretty
powerful analysis you can do with the right information in the trace
buffer.
I think it might be a good idea at some point for those of us using
the VMX tracing (along with those wanting to do SVM tracing) to get
together and define a useful interface.
-George
On 11/3/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
On 3/11/06 04:10, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:
> enhance HVM xentrace:
> 1) VMX xentrace data are store in current vcpu instead physical CPU.
> 2) Log PIO data in xentrace.
>
> Signed-off-by: Xin Li <xin.b.li@xxxxxxxxx>
I was wondering how useful these are at all. It's a bit random and
undocumented. If it's useful perhaps it should be extended into a generic
HVM mechanism and define some processor-agnostic enumerations for exit-code
reasons and so on.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|