RE: [Xen-devel] [PATCH] enhance HVM xentrace

["Li, Xin B" <xin.b.li@xxxxxxxxx>]

>>I was wondering how useful these are at all. It's a bit random and
>>undocumented.
>
>Two usages for us currently:
>1) debug, for some specific bugs it's very useful, for example, the
>issue that win2k can't boot are identified by using xentrace.
>2) outline some specific guest behavior, for example, how HVM guest are
>using it's PIC/LAPIC, so that we may find some optimization
>possibilites.
>
>> 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.
>
>If we could have it, it's really good.
>But for now, I think it's hard and we still need more experiences.

The perl script in the attached patch is to parse VMX xentrace data, and
it helps to shape VMX VMExits with 2 obvious issues:
1) it's specific to VMX currently, and the patch to encode shadow
information into XenTrace data is still in our hand since it's ugly :-(
2) schdule data are not well parsed yet
-Xin

Attachment: parse_vmx_xentrace.patch
Description: parse_vmx_xentrace.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel