WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] enhance HVM xentrace
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Mon, 6 Nov 2006 22:32:01 +0800
Delivery-date: Mon, 06 Nov 2006 06:32:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acb+/gnMn7xz3dqgTCyu9w4PaIkF2QAQRa3LAACDYPAAm2s+AA==
Thread-topic: [Xen-devel] [PATCH] enhance HVM xentrace
>>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
>


The perl script to parse VMX xentrace data is attached, it helps to
shape VMX VMExit, I think maybe we can put it into tools/xentrace/
But 2 obviously 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.pl
Description: parse_vmx_xentrace.pl

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