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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] enhance HVM xentrace
From: "George Dunlap" <gdunlap@xxxxxxxxxxxxx>
Date: Mon, 6 Nov 2006 15:37:49 -0500
Cc: "Li, Xin B" <xin.b.li@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 07 Nov 2006 02:29:43 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=gZWnE2MPiH4uQ3iEYJqv3B/RPBqknm0iWtUuQ2iC3ZHkrqEq71SQbbMix6UuAZZTXDTPmObIHHWAMMsEppA0OZwWHTPPmxhtLc0FC58Oz6B3NI9MXgsIt08kX7JE8jB8PKbeRHhnvU/Psqk7zBOqtpwMgOenzj+aRqWAINpE1E8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C170DEFA.3FB7%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <B30DA1341B0CFA4893EF8A36B40B5C5D59BE1D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C170DEFA.3FB7%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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