[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160726183107.2e7172c6@gandalf.local.home>
Date: Tue, 26 Jul 2016 18:31:07 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Andy Lutomirski <luto@...capital.net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Brian Gerst <brgerst@...il.com>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Byungchul Park <byungchul.park@....com>
Subject: Re: [PATCH 10/19] x86/dumpstack: add get_stack_info() interface
On Tue, 26 Jul 2016 17:24:54 -0500
Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> > This should be impossible unless that last entry is MCE. If we
> > actually fire an event that isn't MCE early in NMI entry, something
> > already went very wrong.
>
> So we don't need to support breakpoints in the early NMI entry code?
Yes, if that happens, then bad things can really happen.
The only way a breakpoint could be added there, is perhaps with KGDB,
and that's just asking for trouble anyway.
-- Steve
Powered by blists - more mailing lists