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] Reuse irq number for virq/ipi after vcpu unplug/

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 04 Feb 2007 04:51:54 +0000
Delivery-date: Sat, 03 Feb 2007 20:51:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F9E11BB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcdHTqIuaJIC5LiAQZGiyexI3PPLIQAyY637
Thread-topic: [Xen-devel] [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug
User-agent: Microsoft-Entourage/11.2.5.060620
On 3/2/07 04:49, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Irq nunmber for per-vcpu event (virq/ipi) needs kept
> accross vcpu plug/unplug, once allocated. We just
> reuse this irq number and bind it to a new event port.
> Or else, /proc/interrupt exports messed statistics
> like:

Noone cares about absolute /proc/interrupt numbers, only rate of change. If
pushed, I would argue that the stats should be zeroed when an interrupt line
is freed (since the interrupt then stops appearing in /proc/interrupts,
which logically implies that the stats lifetime has ended, and so a reuse of
that interrupt is a new lifetime starting from zero). After all, all
irq-evtchn bindings are dynamic running on Xen: a Linux irq may
theoretically get used for all sorts of different devices during the
lifetime of the Linux guest. Should all these uses get aggregated over time?

Zeroing the stats would potentially be a patch for lkml, or we could do it
for dynirqs ourselves in unbind_from_irq(). That's a patch I would accept.

 -- Keir



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