From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: [PATCH 1/5] xen: events: use irq_alloc_desc(_at) instead of open-coding an IRQ allocator. Date: Fri, 29 Oct 2010 11:51:42 -0400 Message-ID: <20101029155142.GB26711@dumpdata.com> References: <1288023736.11153.40.camel@zakaz.uk.xensource.com> <1288023813-31989-1-git-send-email-ian.campbell@citrix.com> <20101025173522.GA5590@dumpdata.com> <4CC60CB7.3070005@goop.org> <20101026141739.GA9557@dumpdata.com> <4CC70583.2050503@goop.org> <20101026170841.GA10708@dumpdata.com> <1739877628.20101028145753@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Ian Campbell , Sander Eikelenboom , Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Konrad@acsinet12.oracle.com List-Id: xen-devel@lists.xenproject.org > > 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. 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.