From: Andy Lutomirski <luto@kernel.org>
To: Borislav Petkov <bp@alien8.de>, Kees Cook <keescook@chromium.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: PCID review?
Date: Tue, 7 Feb 2017 10:56:59 -0800 [thread overview]
Message-ID: <CALCETrVSiS22KLvYxZarexFHa3C7Z-ys_Lt2WV_63b4-tuRpQA@mail.gmail.com> (raw)
Quite a few people have expressed interest in enabling PCID on (x86)
Linux. Here's the code:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=x86/pcid
The main hold-up is that the code needs to be reviewed very carefully.
It's quite subtle. In particular, "x86/mm: Try to preserve old TLB
entries using PCID" ought to be looked at carefully to make sure the
locking is right, but there are plenty of other ways this this could
all break.
Anyone want to take a look or maybe scare up some other reviewers?
(Kees, you seemed *really* excited about getting this in.)
--Andy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-02-07 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 18:56 Andy Lutomirski [this message]
2017-02-07 19:11 ` PCID review? Kees Cook
2017-02-07 19:24 ` Thomas Garnier
2017-02-07 19:37 ` Nadav Amit
2017-02-08 16:24 ` Andy Lutomirski
2017-02-07 21:06 ` Paul E. McKenney
2017-02-08 16:25 ` Andy Lutomirski
2017-02-08 16:52 ` Paul E. McKenney
2017-02-08 20:51 ` Andy Lutomirski
2017-02-09 0:10 ` Mel Gorman
2017-02-10 2:46 ` Andy Lutomirski
2017-02-10 11:01 ` Mel Gorman
2017-02-10 16:44 ` Andy Lutomirski
2017-02-10 21:57 ` Mel Gorman
2017-02-10 22:07 ` Andy Lutomirski
2017-02-10 22:25 ` Borislav Petkov
2017-02-10 22:58 ` Andy Lutomirski
2017-02-13 10:05 ` Mel Gorman
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=CALCETrVSiS22KLvYxZarexFHa3C7Z-ys_Lt2WV_63b4-tuRpQA@mail.gmail.com \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).