On Sat, 19 Feb 2011, KY Srinivasan wrote: > > From: Thomas Gleixner [mailto:tglx@xxxxxxxxxxxxx] > > Please do not use probe_irq_on for dynamic irq allocation. Highjacking > > the lower PIC irqs is really not a good idea. Depending on when this > > runs, you might grab an irq required by a driver which gets loaded > > later. > > > > Could you please explain what you're trying to do here ? > > The IRQ being allocated is for the VMBUS driver for Linux guests running on > a Windows virtualization platform (Hyper-V hypervisor). > The hypervisor is capable of notifying events on the VMBUS via > a guest specified interrupt line. Prior to this patch, > the code was statically selecting an interrupt line for > use by VMBUS. One of the long standing review comments > on that code was to make this irq allocation dynamic and that > is what this patch does. For the Linux guest running as a VM > on Hyper-V, the concern you raise is not an issue. That patch does a whole lot of useless crap. When grabbing some random irq from the PIC is not an issue, then what's the point of this probing, retry loop and the comments about racing ? What races here? That does not make sense at all. I don't know why the previous reviewer wanted to have that dynamic. That just does not make sense to me. Btw, that whole interrupt handler with two tasklets, one of them scheduling work is just screaming threaded interrupt handler. Thanks, tglx _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
