On Wed, Sep 25, 2013 at 04:04:28PM -0700, Linus Torvalds wrote:
> On Wed, Sep 25, 2013 at 9:18 AM, Frederic Weisbecker
> wrote:
> > +#ifdef __ARCH_IRQ_EXIT_ON_IRQ_STACK
>
> Please don't introduce anymore of these insane ad-hoc crazy architecture
> macros.
>
> Just make it a regular config opti
On Wed, Sep 25, 2013 at 9:18 AM, Frederic Weisbecker wrote:
> +#ifdef __ARCH_IRQ_EXIT_ON_IRQ_STACK
Please don't introduce anymore of these insane ad-hoc crazy architecture macros.
Just make it a regular config option, which makes it much easier for
architectures to just select it at config time.
If irq_exit() is called on the arch's specified irq stack,
it should be safe to run softirqs inline under that same
irq stack as it is near empty by the time we call irq_exit().
Hardirqs can nest but irq exit's processing of softirqs only
happen in the inner most hardirq.
So if we use the same st
3 matches
Mail list logo