Yang, Sheng wrote: >> >> You're right, I didn't think it through. >> >> If there was a standard way to mask pci irqs, it might have worked, but >> there isn't, unfortunately. >> >> > What if we got a way to mask pci irqs? We also have to unmask pci irq when > guest wrote EOI to vlapic(or at any other time). I think this still cause > problem. The problem is, we don't know if guest would deassert the line. > Maybe add some time-based detection here might work? > > And about the mask of pci irq, how about disable PCI device interrupt using > Device Control Register bit 10? Not sure if it would affect the pending > transaction, also not sure all device support this (though they should > support). >
I didn't know about this. I'll try to find a copy of the pci spec and read up on it. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
