Re: [PATCH] x86/traps: Don't for in_interrupt() to return true in IST handlers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 24, 2016 at 10:59:45AM +0200, Peter Zijlstra wrote:
> Which use a sequence of: in_nmi(), in_irq(), in_softirq() to pick 1 out
> of 4 possible contexts.

So should we make it cleaner and explicit and define a 5th context of
priorities higher than NMI?

There's some room between those two:

 *             NMI_MASK:        0x00100000
 * PREEMPT_NEED_RESCHED:        0x80000000

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]