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/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH 1/5] xen: events: use irq_alloc_desc(_at) ins

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 1/5] xen: events: use irq_alloc_desc(_at) instead of open-coding an IRQ allocator.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Fri, 29 Oct 2010 11:51:42 -0400
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 29 Oct 2010 08:54:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1010281409290.1407@kaball-desktop>
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: <1288023736.11153.40.camel@xxxxxxxxxxxxxxxxxxxxxx> <1288023813-31989-1-git-send-email-ian.campbell@xxxxxxxxxx> <20101025173522.GA5590@xxxxxxxxxxxx> <4CC60CB7.3070005@xxxxxxxx> <20101026141739.GA9557@xxxxxxxxxxxx> <4CC70583.2050503@xxxxxxxx> <20101026170841.GA10708@xxxxxxxxxxxx> <alpine.DEB.2.00.1010281303330.1407@kaball-desktop> <1739877628.20101028145753@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1010281409290.1407@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
> > So a pvops dom0 kernel all ready seems to require a very recent hypervisor. 
> > So for a dom0 pvops kernel there has to be much less worry about support 
> > for older hypervisors for Xen guests it would only apply for pv domains ?
> > So this could perhaps also be the opportunity to change things ?
> > 
> That is true, however we should try to avoid introducing new
> incompatibilities unless really necessary.

<nods> Especially as there is nothing wrong with using the 4.0 Xen Hypervisor
(released months ago) with 2.6.37.

> In this case it should be sufficient to keep using pirq == gsi for
> gsi < 16.

So we would still need our own interrupt allocation mechanism to
deal with this then.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>