>> 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 <email@example.com>
>I was wondering how useful these are at all. It's a bit random and
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.
Xen-devel mailing list