From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
juerg.haefliger@hpe.com, deepa.srinivasan@oracle.com,
Jim Mattson <jmattson@google.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-mm <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>,
joao.m.martins@oracle.com, pradeep.vincent@oracle.com,
Andi Kleen <ak@linux.intel.com>,
Khalid Aziz <khalid.aziz@oracle.com>,
kanth.ghatraju@oracle.com, Liran Alon <liran.alon@oracle.com>,
Kees Cook <keescook@google.com>,
jsteckli@os.inf.tu-dresden.de,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
chris.hyser@oracle.com, Tyler Hicks <tyhicks@canonical.com>,
John Haxby <john.haxby@oracle.com>, Jon Masters <jcm@redhat.com>
Subject: Re: Redoing eXclusive Page Frame Ownership (XPFO) with isolated CPUs in mind (for KVM to isolate its guests per CPU)
Date: Tue, 21 Aug 2018 10:57:03 +0100 [thread overview]
Message-ID: <1534845423.10027.44.camel@infradead.org> (raw)
In-Reply-To: <CA+55aFxyUdhYjnQdnmWAt8tTwn4HQ1xz3SAMZJiawkLpMiJ_+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Mon, 2018-08-20 at 15:27 -0700, Linus Torvalds wrote:
> On Mon, Aug 20, 2018 at 3:02 PM Woodhouse, David <dwmw@amazon.co.uk> wrote:
> >
> > It's the *kernel* we don't want being able to access those pages,
> > because of the multitude of unfixable cache load gadgets.
>
> Ahh.
>
> I guess the proof is in the pudding. Did somebody try to forward-port
> that patch set and see what the performance is like?
I hadn't actually seen the XPFO patch set before; we're going to take a
serious look.
Of course, this is only really something that a select few people (with
quite a lot of machines) would turn on. And they might be willing to
tolerate a significant performance cost if the alternative way to be
safe is to disable hyperthreading entirely — which is Intel's best
recommendation so far, it seems.
Another alternative... I'm told POWER8 does an interesting thing with
hyperthreading and gang scheduling for KVM. The host kernel doesn't
actually *see* the hyperthreads at all, and KVM just launches the full
set of siblings when it enters a guest, and gathers them again when any
of them exits. That's definitely worth investigating as an option for
x86, too.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-08-21 9:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 21:25 Redoing eXclusive Page Frame Ownership (XPFO) with isolated CPUs in mind (for KVM to isolate its guests per CPU) Konrad Rzeszutek Wilk
2018-08-20 21:48 ` Linus Torvalds
2018-08-20 21:52 ` Woodhouse, David
2018-08-20 22:18 ` Kees Cook
2018-08-20 22:27 ` Linus Torvalds
2018-08-20 22:35 ` Tycho Andersen
2018-08-20 22:59 ` Dave Hansen
2018-08-20 23:14 ` David Woodhouse
2018-08-20 23:26 ` Dave Hansen
2018-08-20 23:38 ` Linus Torvalds
2018-08-21 9:57 ` David Woodhouse [this message]
2018-08-21 14:01 ` Liran Alon
2018-08-21 14:22 ` David Woodhouse
2018-08-21 23:04 ` Liran Alon
2018-08-30 16:00 ` Julian Stecklina
2018-08-31 15:26 ` Tycho Andersen
2018-09-01 21:38 ` Linus Torvalds
2018-09-01 22:33 ` Wes Turner
2018-09-03 15:36 ` Andi Kleen
2018-09-03 14:51 ` Julian Stecklina
2018-09-12 15:37 ` Julian Stecklina
2018-09-13 6:11 ` Juerg Haefliger
2018-09-17 10:01 ` Julian Stecklina
2018-09-17 10:19 ` Tycho Andersen
2018-09-17 13:27 ` Christoph Hellwig
2018-09-14 17:06 ` Khalid Aziz
2018-09-17 9:51 ` Julian Stecklina
2018-09-18 23:00 ` Khalid Aziz
2018-09-24 14:45 ` Stecklina, Julian
2018-10-15 8:07 ` Khalid Aziz
2018-10-24 11:00 ` Khalid Aziz
2018-10-24 15:00 ` Tycho Andersen
2018-09-03 15:26 ` Andi Kleen
2018-09-04 9:37 ` Julian Stecklina
2018-09-07 21:30 ` Khalid Aziz
2018-08-31 8:43 ` James Bottomley
2018-09-19 1:03 ` Balbir Singh
2018-09-19 15:34 ` Jonathan Adams
2018-09-19 15:38 ` Jonathan Adams
2018-09-19 15:43 ` Jonathan Adams
2018-09-23 2:33 ` Balbir Singh
2018-09-25 14:12 ` Stecklina, Julian
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=1534845423.10027.44.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=ak@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chris.hyser@oracle.com \
--cc=deepa.srinivasan@oracle.com \
--cc=jcm@redhat.com \
--cc=jmattson@google.com \
--cc=joao.m.martins@oracle.com \
--cc=john.haxby@oracle.com \
--cc=jsteckli@os.inf.tu-dresden.de \
--cc=juerg.haefliger@hpe.com \
--cc=kanth.ghatraju@oracle.com \
--cc=keescook@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=khalid.aziz@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liran.alon@oracle.com \
--cc=pradeep.vincent@oracle.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tyhicks@canonical.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).