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: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] add long interrupt measurement capability
From: Dulloor <dulloor@xxxxxxxxx>
Date: Sat, 9 May 2009 05:12:14 -0400
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Delivery-date: Sat, 09 May 2009 02:12:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=fsmRsTHR5vz8JZCwxb65WBYUmp/1EvW4XYUU6nWBaCM=; b=HCs/3dcu/m2sqA6Z6EBPvY1l8CRQuUir95jFluLC1p14TP3e9Sjl4qGXVuQTeyw+SI DRg3goBono/Hm0i9cizJsgdXr5DLrevJahb4ssfA1DLtpEVfEZcLCq2/RHBGGs2jkuQ0 vvQ6UbfQ/silqbd+Ewtg5SzXrB0l+PAT1pEmM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YHHaRCoAGQvbqIUwSoWDUlfhh4nebWzG/9rk/do5aEnTVZu9SsHOLjjjOkQVc7AzbH nQ0oU+Rk95bSzKApk7AhOMLrIBezKUWlGCLDYV7BBPdyZA0Xy5SbyuBMuNuhO5kjCOVB PnVATLdao7+ULrTn3jm+bgdvg2pYoZfbe7m50=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C62AF5A5.A80D%keir.fraser@xxxxxxxxxxxxx>
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>
References: <4FA716B1526C7C4DB0375C6DADBC4EA3417372CDD1@xxxxxxxxxxxxxxxxxxxxxxxxx> <C62AF5A5.A80D%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Here is a xentrace patch.

- Should irq_desc_measure_t move to some .h file ?
- I have defined the new trace event in general class. Is it fine ?

- I have defined tsc_in as volatile to avoid initializing it in the main code path.

thanks
dulloor

On Sat, May 9, 2009 at 3:56 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
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



Attachment: measure_irq.patch
Description: Text Data

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