Re: [PATCH v4 2/5] x86, traps: Track entry into and exit from IST context

From: Andy Lutomirski
Date: Wed Dec 10 2014 - 19:25:17 EST

On Wed, Dec 10, 2014 at 4:22 PM, Tony Luck <tony.luck@xxxxxxxxx> wrote:
> On Tue, Nov 25, 2014 at 10:58 AM, Borislav Petkov <bp@xxxxxxxxx> wrote:
>> On Mon, Nov 24, 2014 at 03:52:10PM -0800, Andy Lutomirski wrote:
>>> Dunno. Tony and Borislav -- when do you want the IST stack switching
>>> stuff?
>> I'd leave that up to Tony and his testbench. I mean, we can hammer on
>> it as much as we can and it can pass all testing locally but the real
>> fun starts once it hits upstream and for that it doesn't matter which
>> release... IMHO.
> So what was the net result of all the mode/RCU discussions?
> Do I need some extra magic incantations in the final version
> of do_machine_check() beyond what was in this patch:
> to make everything happy?

I think you need ist_begin_non_atomic() before local_irq_enable() and
ist_end_non_atomic() after local_irq_disable(). Otherwise it should
be good.


> -Tony

Andy Lutomirski
AMA Capital Management, LLC
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at