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

RE: [Xen-devel] Multiple IRQ's in HVM for Windows


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sat, 27 Dec 2008 20:35:33 +1100
  • Cc:
  • Delivery-date: Sat, 27 Dec 2008 01:36:03 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclnCjPkeAYvm5WbTaqM+PmGGNFiHQAIdYQ3AAU6BeAAATbLsQAADYFAAADLT9kALf9OEAABLL7gAAAL4JA=
  • Thread-topic: [Xen-devel] Multiple IRQ's in HVM for Windows

> On 27/12/2008 09:19, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > I can think of the following pieces of the puzzle:
> > . A mechanism to assign an event channel to an IRQ - a new type of
> > parameter for HYPERVISOR_hvm_op?
> 
> That's part of the problem. What do you mean by 'IRQ' here? What's the
IRQ
> namespace that you're indexing into?
> 

I'm not sure if I understand the question. Under my drivers I just do:

hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, irq_number);

where irq_number is what Windows assigns the platform PCI device, and is
normally 28 when the HAL is APIC, otherwise it is 5, assuming no qemu
network adapters or passed through PCI devices.

I think there is another way of setting the IRQ using the PCI address,
but that doesn't appear to be required here.

James

_______________________________________________
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®.