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] Binding ISA Irq seems to malfunction in Xen 3.4

To: "Tom Rotenberg" <tom.rotenberg@xxxxxxxxx>
Subject: Re: [Xen-devel] Binding ISA Irq seems to malfunction in Xen 3.4
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 13 Nov 2009 09:22:02 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Nov 2009 01:22:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8686c3cd0911120951s158d00c9je1df75ec86bfef60@xxxxxxxxxxxxxx>
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: <8686c3cd0911120951s158d00c9je1df75ec86bfef60@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Tom Rotenberg <tom.rotenberg@xxxxxxxxx> 12.11.09 18:51 >>>
>I'm trying to use the function: 'xc_domain_bind_pt_isa_irq()', in
>order to bind the real machine irq of the keyboard & mouse (interrupts
>12 & 1), to a specific domain, so he will be ale to use the PS2
>keyboard & mouse in pass-through.
>Howeverm when i perform the call to the 'xc_domain_bind_pt_isa_irq()',
>i keep getting an error code, and the function fails to bind the
>interrupt. I also, performed a search, and found that no-one is using
>this function, so i'm afarid that this function doesn't work at all.
>I also want to know, how can i debug this problem? Could it be related
>to the fact that the interrupt i'm trying to bind, is already
>"connected" do dom0 (as he uses the keyboard & mouse)?
>Can someone please help me with this?

You obviously first need to make sure Dom0 doesn't use the IRQ - for
one ISA IRQs are not shareable, but more importantly you really don't
intend to have two domains drive the same hardware, do you? And
you may have some difficulty doing so since (without patching the code)
you can't even configure the Dom0 kernel to not have an 8042 driver
on x86 (unless you select EMBEDDED), i.e. it will always attach to the
device if there is one.


Xen-devel mailing list