From: Dave Hansen <dave.hansen@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
David Vrabel <david.vrabel@citrix.com>,
linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH] x86: skip check for spurious faults for non-present faults
Date: Fri, 16 May 2014 09:54:40 -0700 [thread overview]
Message-ID: <537642D0.60105@intel.com> (raw)
In-Reply-To: <2edd49ee-077e-4126-b09a-077b7f6be553@email.android.com>
On 05/15/2014 02:20 PM, H. Peter Anvin wrote:
> I'm trying to wrap my head around any forward compatibility
> concerns... if we misidentify a fault as spurious that would be bad.
FWIW, I did go through the bullets in the SDM's "4.10.4.3 Optional
Invalidation". The only condition not covered by this patch is the one
that talks about "CR4.SMEP = 0...".
But, I don't know of any case where we take a userspace page and make it
supervisor-only, so I don't think this is possible now.
prev parent reply other threads:[~2014-05-16 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 10:29 [PATCH] x86: skip check for spurious faults for non-present faults David Vrabel
2014-05-15 20:50 ` Dave Hansen
2014-05-15 21:20 ` H. Peter Anvin
2014-05-16 16:54 ` Dave Hansen [this message]
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=537642D0.60105@intel.com \
--to=dave.hansen@intel.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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