[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
  • Date: Fri, 3 Nov 2006 20:19:10 +0800
  • Delivery-date: Fri, 03 Nov 2006 04:19:45 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acb+/gnMn7xz3dqgTCyu9w4PaIkF2QAQRa3LAACDYPA=
  • Thread-topic: [Xen-devel] [PATCH] enhance HVM xentrace

>> 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.

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.
-Xin

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.