Thanks for the explanation, and for the -pre9 version - I'll give it a try next time I get chance...
-Nick
>>> On 2008/07/19 at 21:43, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:
> James, I'm still curious on the question someone else asked about why the > Xen devices show up on the ISA bus? I know it probably doesn't really > make a difference, since it is "virtual" hardware, but that just seems a > little strange. Definitely not a criticism, just curious about it...
The interrupts that those devices use are virtual and are nothing to do with the PCI interrupt that the xenpci driver uses. They are triggered by calling an asm 'int x' instruction from the xenpci driver. It would be nice to be able to use the PCI interrupts, as there are more of them available and there are performance improvements to be had by using non-shared interrupts, but when I ask the Windows PnP manager for an interrupt it appears that I can only ask for one in the range of 1-15, and for various reasons, 2, 7, 9, and 15 don't work. 2 and 9 because of the way the ISA interrupt controllers link to each other, and 7 and 15 for reasons that I can't remember right now.
If I ask for an interrupt in the range 16-63, windows won't give me one. I can't just use a 16-63 interrupt without allocating them as I need the PnP manager to set up the irq vector properly. This is the problem of trying to interface with closed source code like Windows - you are stuck with what you get :)
I think 'ISA' in this case just means a non-APIC sourced interrupt, the xen devices are on an 'Internal' bus as far as Windows is concerned.
James
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|