From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Matt Fleming <matt@console-pimps.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: EFI mixed mode + perf = rampant triple faults
Date: Wed, 14 Jan 2015 19:47:14 +0100 [thread overview]
Message-ID: <20150114184714.GD6902@pd.tnic> (raw)
In-Reply-To: <CALCETrUEfQY-hnmNV9-PfDbEYLa7bVoRcsZc2X0V+mEAbfNH2g@mail.gmail.com>
On Wed, Jan 14, 2015 at 10:38:25AM -0800, Andy Lutomirski wrote:
> That's not a real MCE, though -- it happens synchronously instead of
MCE can be synchronous in a sense too, as a result of executing an insn,
for example, i.e., EIPV bit set.
> at MCE priority with all the associated messiness. Or is the idea to
> just stick that in after switching to the 32-bit mode being tested?
Yes, the idea was to simply trigger a real exception after switching to
32-bit while still with 64-bit IDT handlers.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2015-01-14 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 16:51 EFI mixed mode + perf = rampant triple faults Andy Lutomirski
2014-12-17 16:54 ` Andy Lutomirski
2014-12-31 18:37 ` Matt Fleming
2015-01-14 16:51 ` Matt Fleming
2015-01-14 18:27 ` Andy Lutomirski
2015-01-14 18:35 ` Borislav Petkov
2015-01-14 18:38 ` Andy Lutomirski
2015-01-14 18:47 ` Borislav Petkov [this message]
2015-01-14 18:49 ` Andy Lutomirski
2015-01-15 19:41 ` Matt Fleming
2015-01-15 19:59 ` H. Peter Anvin
2015-01-15 22:21 ` Matt Fleming
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=20150114184714.GD6902@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=matt@console-pimps.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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