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
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).
> 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.
Xen-devel mailing list