[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Binding ISA Irq seems to malfunction in Xen 3.4


  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
  • Date: Fri, 13 Nov 2009 12:19:28 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 13 Nov 2009 02:19:48 -0800
  • 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=V5J0ubNR4XRrtWPC17KxCFgQ+2n4TWN7FZUdBipHhlLkXJMBWVcH53dD8tEsWwQSaw 6i4Zoj6BOMoOZ9znbQbe8G3rGzdMR3ky0pRYIdgTQyKxHhKefht2f9RyvJ2Gzdx9BOS2 OPP2id4LAyQM2IgnEe73AkV+o5Kr/8KDA1zUA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I understand...

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?

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.