On Tue, Apr 22 2008, Avi Kivity wrote: > Jens Axboe wrote: > >>Introducing this fallback will make any usage from irq disabled context > >>deadlock prone. > >> > >>I rather like the current interface. > >> > > > >Hmm good point, I'll back that bit out again. > > > > But then you need to fix all callers to handle errors. They should already, there were various error conditions before depending on the arch. I'm aware that some do not, so I'd consider that a general cleanup (that must also be done, agree). > Perhaps we need a new flag for failable async IPIs (or better, API). > I'm pretty sure no one uses s_c_f_s() from irq disabled context on x86, > since it will WARN_ON(irqs_disabled()). That'd work. I tried to keep things really simple here, I have other ideas for cleanups and improvements once this batch goes in. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
