From: David Woodhouse <dwmw2@infradead.org>
To: mingo@kernel.org, hpa@zytor.com, tim.c.chen@linux.intel.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
luto@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [tip:x86/pti] x86/speculation: Use Indirect Branch Prediction Barrier in context switch
Date: Mon, 05 Feb 2018 14:18:29 +0000 [thread overview]
Message-ID: <1517840309.31953.153.camel@infradead.org> (raw)
In-Reply-To: <tip-18bf3c3ea8ece8f03b6fc58508f2dfd23c7711c7@git.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
On Tue, 2018-01-30 at 14:39 -0800, tip-bot for Tim Chen wrote:
> Thanks to the reviewers and Andy Lutomirski for the suggestion of
> using ctx_id which got rid of the problem of mm pointer recycling.
That one doesn't backport well to 4.9. Suggestions welcome.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-02-05 14:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:04 [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier in context switch David Woodhouse
2018-01-30 17:48 ` Josh Poimboeuf
2018-01-30 21:23 ` Tim Chen
2018-01-30 22:00 ` Borislav Petkov
2018-01-30 22:21 ` Thomas Gleixner
2018-01-30 22:55 ` Borislav Petkov
2018-01-31 3:59 ` Josh Poimboeuf
2018-01-31 23:25 ` Tim Chen
2018-01-30 20:38 ` Borislav Petkov
2018-01-30 21:03 ` Tim Chen
2018-01-30 21:57 ` Borislav Petkov
2018-01-30 22:26 ` Tim Chen
2018-01-30 22:43 ` Borislav Petkov
2018-01-31 0:25 ` Tim Chen
2018-01-31 0:41 ` Borislav Petkov
2018-01-30 22:39 ` [tip:x86/pti] " tip-bot for Tim Chen
2018-01-31 7:03 ` Dominik Brodowski
2018-01-31 13:24 ` Josh Poimboeuf
2018-02-01 8:25 ` Christian Brauner
2018-02-01 8:31 ` David Woodhouse
2018-02-01 15:40 ` Josh Poimboeuf
2018-02-04 19:39 ` Dominik Brodowski
2018-02-05 14:18 ` David Woodhouse [this message]
2018-02-05 19:35 ` Tim Chen
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=1517840309.31953.153.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.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).