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] Re: [PATCH] add long interrupt measurement capability

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Dulloor <dulloor@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] add long interrupt measurement capability
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sat, 09 May 2009 08:56:05 +0100
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 09 May 2009 00:56:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4FA716B1526C7C4DB0375C6DADBC4EA3417372CDD1@xxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnQJTWUPFXimfVuTqSgp1PQjogQzAAAE0TAABWF/Rk=
Thread-topic: [Xen-devel] Re: [PATCH] add long interrupt measurement capability
User-agent: Microsoft-Entourage/12.17.0.090302
On 08/05/2009 22:53, "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx> wrote:

>> Perhaps.  However measuring cycles is important and, more
>> specifically, measuring MAX cycles spent across a set of
>> interrupts.  As a result, I suspect any code that measures
>> this (regardless of whether the result is reported by
>> xentrace or debug-key) would likely encounter the
>> same objection from Keir.
> 
> I can't imagine there'd be any objection to adding trace macros to record
> this. The xentrace log processing tool can then be updated to generate max or
> histogram values.

Yes, xentrace records would be okay. It's adding another debug key and
printing to Xen console for this purpose which I do not think is worthwhile.

 -- Keir



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