All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, luto@kernel.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 0/3] x86, pkeys: fix prefetch/pkeys interaction
Date: Fri, 22 Jul 2016 11:03:10 -0700	[thread overview]
Message-ID: <20160722180310.99F5BCFF@viggo.jf.intel.com> (raw)

The first two patches here are useful in any case, I think.

But, as for the third:  There are no known prefetch errata on
processors that support memory protection keys.  There have not
been any that I can find in any recent generations, either.

But, if there were a future erratum, we would need this.
Otherwise, apps who hit the theoretical erratum and used pkeys
would not be fixed up by the prefetch erratum detection code.

It also occurs to me that *if* there were an erratum on a modern
CPU, we might not know because we have so many workarounds in
place.

So, I'm submitting this, but I don't feel that strongly about it.
It doesn't fix a real problem, but it's also not that much code,
or in any kind of fast path.

             reply	other threads:[~2016-07-22 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 18:03 Dave Hansen [this message]
2016-07-22 18:03 ` [PATCH 1/3] x86, tracing: fix x86 exceptions trace header Dave Hansen
2016-07-29 15:08   ` Steven Rostedt
2016-07-22 18:03 ` [PATCH 2/3] x86: add some better documentation for probe_kernel_address() Dave Hansen
2016-07-22 18:10   ` Andy Lutomirski
2016-07-22 18:18     ` Dave Hansen
2016-07-22 18:22       ` Andy Lutomirski
2016-07-22 18:03 ` [PATCH 3/3] x86, pkeys: allow instruction fetches in presence of pkeys Dave Hansen

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=20160722180310.99F5BCFF@viggo.jf.intel.com \
    --to=dave@sr71.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.