[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] Interrupt forwarding
> > We don't go that far. A sensible approach would be to require the > > driver to be restarted, and to reset the hardware device, before > > unmasking. Or to rate limit each interrupt line to an > > administrator-configurable 'reasonable' number of IRQs per second -- > > this might also catch bugs where drivers are not properly acking > > devices for other reasons. > > In x86 boxes almost everything is shared. Leaving the interrupt masked > off will probably disable 20% of the hardware in the box. That's not my experience, certainly on modern server hardware. On systems with an IOAPIC its rare to see a shared interrupt, and even if you do you can typically avoid it just by swapping a couple of PCI cards around. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |