From: Ingo Molnar <mingo@kernel.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Salman Qazi <sqazi@google.com>, Ingo Molnar <mingo@elte.hu>,
Michal Hocko <mhocko@suse.cz>, Borislav Petkov <bp@alien8.de>,
Vojtech Pavlik <vojtech@suse.cz>, Petr Tesarik <ptesarik@suse.cz>,
Petr Mladek <pmladek@suse.cz>
Subject: Re: 64bit x86: NMI nesting still buggy?
Date: Tue, 6 May 2014 12:02:18 +0200 [thread overview]
Message-ID: <20140506100217.GA27774@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1404291720440.16783@pobox.suse.cz>
* Jiri Kosina <jkosina@suse.cz> wrote:
> On Tue, 29 Apr 2014, Steven Rostedt wrote:
>
> > > According to 38.4 of [1], when SMM mode is entered while the CPU is
> > > handling NMI, the end result might be that upon exit from SMM, NMIs will
> > > be re-enabled and latched NMI delivered as nested [2].
> >
> > Note, if this were true, then the x86_64 hardware would be extremely
> > buggy. That's because NMIs are not made to be nested. If SMM's come in
> > during an NMI and re-enables the NMI, then *all* software would break.
> > That would basically make NMIs useless.
> >
> > The only time I've ever witness problems (and I stress NMIs all the
> > time), is when the NMI itself does a fault. Which my patch set handles
> > properly.
>
> Yes, it indeed does.
>
> In the scenario I have outlined, the race window is extremely small,
> plus NMIs don't happen that often, plus SMIs don't happen that
> often, plus (hopefully) many BIOSes don't enable NMIs upon SMM exit.
Note, the "NMIs don't happen that often" condition is pretty rare on
x86 Linux systems. These days anyone doing a 'perf top', 'perf record'
or running a profiling tool like SysProf will generate tens of
thousands of NMIs, per second. Systems with profiling active are
literally bathed in NMIs, and that is how we found the page fault NMI
bug.
So I'd say any race condition hypothesis assuming "NMIs are rare" is
probably invalid on modern Linux systems.
Thanks,
Ingo
next prev parent reply other threads:[~2014-05-06 10:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 13:05 64bit x86: NMI nesting still buggy? Jiri Kosina
2014-04-29 13:29 ` H. Peter Anvin
2014-04-29 14:06 ` Steven Rostedt
2014-04-29 14:28 ` H. Peter Anvin
2014-04-29 14:31 ` Petr Tesarik
2014-04-30 22:10 ` Jiri Kosina
2014-04-30 22:46 ` H. Peter Anvin
2014-04-29 14:03 ` Steven Rostedt
2014-04-29 15:24 ` Jiri Kosina
2014-04-29 15:41 ` Vojtech Pavlik
2014-04-29 16:09 ` Steven Rostedt
2014-04-29 16:19 ` Steven Rostedt
2014-04-29 16:51 ` Jiri Kosina
2014-04-29 17:12 ` Steven Rostedt
2014-04-29 18:48 ` Jiri Kosina
2014-04-29 19:16 ` Steven Rostedt
2014-05-06 10:02 ` Ingo Molnar [this message]
2014-05-21 13:42 ` Jiri Kosina
2014-05-21 14:20 ` Borislav Petkov
2014-05-21 14:58 ` Vojtech Pavlik
2014-05-21 15:22 ` Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140506100217.GA27774@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@elte.hu \
--cc=pmladek@suse.cz \
--cc=ptesarik@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sqazi@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vojtech@suse.cz \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox