Messages in this thread | | | Date | Sat, 19 Jun 2010 09:51:01 +0800 | Subject | Re: [RFC 1/3] Unified NMI delayed call mechanism | From | huang ying <> |
| |
On Fri, Jun 18, 2010 at 11:31 PM, Peter Zijlstra <peterz@infradead.org> wrote: > On Fri, 2010-06-18 at 23:16 +0800, huang ying wrote: >> >> soft_irq is a delayed mechanism for IRQ, > > No its not.
Why? What do you think soft_irq is for?
>> a self interrupt can be a >> delayed mechanism for NMI. If we can make soft_irq NMI-safe, > > No you can't. > >> we can >> use soft_irq as a backup of self interrupt (for systems without APIC >> and maybe for other architectures). > > Whatever would you want to do that for.
Best Regards, Huang Ying -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |