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: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Binding ISA Irq seems to malfunction in Xen 3.4
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Fri, 13 Nov 2009 12:27:45 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Nov 2009 02:28:06 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=EHV5TWBio7lSBjsPKsGyyVmS2tsi0ZB2YCwAQaBTdxk=; b=Q/ZlHMVdn2oM1jJZ/tXt43GdMh39M7K8a/LRbHStDsEoqR5EhuUPUcRAc/tDZZR+t8 nZmdFTbmxUCESl+de3rA4Qwop5MPea88FghdS41HHwf7sln20GNPbq71pGIfNuA2Alms P2IKHaISNVm2ylqAiSaZaTZkORse7XMCiPUjU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=q7DGwNcOe9nRdPEiv7S2o4YnhJ5KXbIsD0Kbf912w1DO66Paahs6HP878Xk5O1Nkkr h6jq3kMqQ+5h1qSCC606lKkMz10/fjGANV07Wt+CYAah1uf1y/u2sNJnC4T0yMIBNONW C5Sig9WQmXjrY9p+jlVcJLyolQazj8zvGUUBU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AFD41AC020000780001F87C@xxxxxxxxxxxxxxxxxx>
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> <4AFD334A020000780001F7F5@xxxxxxxxxxxxxxxxxx> <8686c3cd0911130219p4cf87b5csf4a7f9ecbb29b00b@xxxxxxxxxxxxxx> <4AFD41AC020000780001F87C@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
So, the only way to do this, is to compile the dom0 kernel, with the
'EMBEDDED' (CONFIG_EMBEDDED?) option, and then to try to bind those
ISA interrupts?

Do u have any idea, how the code in XCI implements this?

On Fri, Nov 13, 2009 at 12:23 PM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>> Tom Rotenberg <tom.rotenberg@xxxxxxxxx> 13.11.09 11:19 >>>
>>and can i compile the i8042 module, as a loadable kernel module
>>(instead of staticly in the kernel), and then simply 'rmmod' the i8042
>>module, and it will work?
> No, you're not being presented with the config option prompt to select
> it to be a module (otherwise you would also be able to turn it off).
> Jan
> On Fri, Nov 13, 2009 at 11:22 AM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>>> 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.
>> Jan

Xen-devel mailing list