From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: STI architectural question (and lretq -- I'm not even kidding)
Date: Wed, 23 Jul 2014 12:49:17 +0200 [thread overview]
Message-ID: <20140723104917.GB23102@pd.tnic> (raw)
In-Reply-To: <CALCETrUjKXfwbWkUytMXLSmKROLBVY7tRYWPHnEC01Fj=aiTkQ@mail.gmail.com>
On Tue, Jul 22, 2014 at 06:33:02PM -0700, Andy Lutomirski wrote:
> Of course, this does nothing at all to protect us from #MC after sti
> on return from #MC to userspace, but I think we're screwed regardless
> -- we could just as easily get a second #MC before the sti. Machine
> check broadcast was the worst idea ever.
Please do not think that a raised #MC means the machine is gone. There
are MC errors which are reported with the exception mechanism and from
which we can and do recover, regardless of broadcasting or not.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-07-23 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 0:10 STI architectural question (and lretq -- I'm not even kidding) Andy Lutomirski
2014-07-23 1:03 ` Linus Torvalds
2014-07-23 1:33 ` Andy Lutomirski
2014-07-23 10:49 ` Borislav Petkov [this message]
2014-07-23 15:12 ` Andy Lutomirski
2014-07-23 15:23 ` Borislav Petkov
2014-07-23 9:40 ` Borislav Petkov
2014-07-23 21:18 ` Andi Kleen
2014-07-23 21:52 ` Andy Lutomirski
2014-07-23 23:10 ` Andi Kleen
2014-07-24 22:15 ` H. Peter Anvin
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=20140723104917.GB23102@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).