From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH v3 0/4] L1TF KVM ARCH_CAPABILITIES #0
Date: Sun, 5 Aug 2018 18:31:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808051740440.17359@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180805140747.22303-1-pbonzini@redhat.com>
Paolo,
On Sun, 5 Aug 2018, speck for Paolo Bonzini wrote:
> Support for ARCH_CAPABILITIES bit 3, which can already be used to disable
> the mitigations on a nested hypervisor. Patch 1 is already in Linus's
> tree.
It's also in 4.17 stable, but 4.14 stable lacks it. IIRC you wanted to post
a list of upstream commits which are prerequisite for bringing that in. I
worked my way through it and picked out the following commits:
518e7b94817a ("KVM: X86: Allow userspace to define the microcode version")
66421c1ec340 ("KVM: X86: Introduce kvm_get_msr_feature()")
d1d93fa90f1a ("KVM: SVM: Add MSR-based feature support for serializing LFENCE")
801e459a6f3a ("KVM: x86: Add a framework for supporting MSR-based features")
The LFENCE and UCODE one are not really required, but I thought they are
useful in context of this mess.
Thanks,
tglx
prev parent reply other threads:[~2018-08-05 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 14:07 [MODERATED] [PATCH v3 0/4] L1TF KVM ARCH_CAPABILITIES #0 Paolo Bonzini
2018-08-05 14:07 ` [MODERATED] [PATCH v3 1/4] L1TF KVM ARCH_CAPABILITIES #1 Paolo Bonzini
2018-08-05 14:07 ` [MODERATED] [PATCH v3 2/4] L1TF KVM ARCH_CAPABILITIES #2 Paolo Bonzini
2018-08-05 14:07 ` [MODERATED] [PATCH v3 3/4] L1TF KVM ARCH_CAPABILITIES #3 Paolo Bonzini
2018-08-05 14:07 ` [MODERATED] [PATCH v3 4/4] L1TF KVM ARCH_CAPABILITIES #4 Paolo Bonzini
2018-08-05 16:31 ` Thomas Gleixner [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=alpine.DEB.2.21.1808051740440.17359@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).