From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xen 4 only seeing one keyboard and mouse
Date: Mon, 23 Aug 2010 10:24:24 -0400
Message-ID: <20100823142424.GA5955@phenom.dumpdata.com>
References: <alpine.LFD.2.00.1007212256550.16590@vega1.dur.ac.uk>
	<20100722175153.GA4911@phenom.dumpdata.com>
	<alpine.LFD.2.00.1007221925480.6600@vega1.dur.ac.uk>
	<20100723142724.GB4008@phenom.dumpdata.com>
	<alpine.LFD.2.00.1008081943300.23208@vega3.dur.ac.uk>
	<alpine.LFD.2.00.1008082108120.25685@vega3.dur.ac.uk>
	<20100816154618.GA8493@phenom.dumpdata.com>
	<alpine.LFD.2.00.1008162202140.11400@vega1.dur.ac.uk>
	<20100816223354.GA4237@phenom.dumpdata.com>
	<alpine.LFD.2.00.1008212010490.25583@vega3.dur.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.00.1008212010490.25583@vega3.dur.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Sat, Aug 21, 2010 at 10:00:37PM +0100, M A Young wrote:
> On Mon, 16 Aug 2010, Konrad Rzeszutek Wilk wrote:
> 
> >The one thing that is odd is that in 4.0 we start with vector 0x28 while
> >in 3.4 it is with 0x20.
> >
> >It looks as if one vector is getten eaten. But that should not be such
> >an issue as the internal mapping of vector->irq is still proper...
> 
> I can tell you why that happens.
> For 3.4 new vectors are allocated in the order 32,40,...,216 then
> 33,41,... etc. in assign_irq_vector from xen/arch/x86/irq.c
> For 4.0 new vectors are allocated in the order 40,48,...,216 then
> 33,41,... etc. in __assign_irq_vector from xen/arch/x86/irq.c
> So for 4.0 the allocation of vector 32 is never attempted, but as it
> is already reserved for IRQ_MOVE_CLEANUP_VECTOR this shouldn't
> matter.

Argh. So red-heering then.