From: Paolo Bonzini <pbonzini@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v7 0/5] NX 0
Date: Thu, 24 Oct 2019 20:56:23 +0200 [thread overview]
Message-ID: <1ba3f78a-3edf-43a8-98b1-24176c7cbf81@redhat.com> (raw)
In-Reply-To: <abe0cd1da2d3ba76cbca8085d075df05d24781e8.camel@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
On 24/10/19 20:27, speck for Ben Hutchings wrote:
> On Thu, 2019-10-24 at 18:34 +0200, speck for Paolo Bonzini wrote:
>> From: Paolo Bonzini <pbonzini@redhat.com>
>> Subject: [PATCH v7 0/5] NX 0
>>
>>
>> v6->v7: tell nested hypervisors to disable the mitigation
>
> Does that eliminate the need to patch qemu?
No, it *introduces* the need to patch QEMU (because QEMU now can choose
to enable that bit in MSR_IA32_ARCH_CAPABILITIES; before, it need not
know about the bit).
Paolo
> Ben.
>
>> Junaid Shahid (2):
>> kvm: Add helper function for creating VM worker threads
>> kvm: x86: mmu: Recovery of shattered NX large pages
>>
>> Paolo Bonzini (1):
>> kvm: mmu: ITLB_MULTIHIT mitigation
>>
>> Pawan Gupta (2):
>> x86: Add ITLB_MULTIHIT bug infrastructure
>> x86/cpu: Add Tremont to the cpu vulnerability whitelist
>>
>> Documentation/ABI/testing/sysfs-devices-system-cpu | 1 +
>> Documentation/admin-guide/kernel-parameters.txt | 17 ++
>> arch/x86/include/asm/cpufeatures.h | 1 +
>> arch/x86/include/asm/kvm_host.h | 6 +
>> arch/x86/include/asm/msr-index.h | 7 +
>> arch/x86/kernel/cpu/bugs.c | 24 ++
>> arch/x86/kernel/cpu/common.c | 73 +++---
>> arch/x86/kvm/mmu.c | 264 ++++++++++++++++++++-
>> arch/x86/kvm/mmu.h | 4 +
>> arch/x86/kvm/paging_tmpl.h | 29 ++-
>> arch/x86/kvm/x86.c | 20 ++
>> drivers/base/cpu.c | 8 +
>> include/linux/cpu.h | 2 +
>> include/linux/kvm_host.h | 6 +
>> virt/kvm/kvm_main.c | 114 ++++++++-
>> 15 files changed, 530 insertions(+), 46 deletions(-)
>>
prev parent reply other threads:[~2019-10-24 18:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 16:34 [MODERATED] [PATCH v7 0/5] NX 0 Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 1/5] NX 1 Paolo Bonzini
2019-10-30 18:38 ` [MODERATED] " Josh Poimboeuf
2019-10-31 11:05 ` Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 2/5] NX 2 Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 3/5] NX 3 Paolo Bonzini
2019-10-25 8:37 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-25 8:48 ` Paolo Bonzini
2019-10-25 9:03 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-25 9:08 ` Paolo Bonzini
2019-10-25 9:45 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-25 10:39 ` Paolo Bonzini
2019-10-29 20:33 ` mark gross
2019-10-31 11:02 ` Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 4/5] NX 4 Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 5/5] NX 5 Paolo Bonzini
2019-10-24 18:27 ` [MODERATED] Re: [PATCH v7 0/5] NX 0 Ben Hutchings
2019-10-24 18:56 ` Paolo Bonzini [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=1ba3f78a-3edf-43a8-98b1-24176c7cbf81@redhat.com \
--to=pbonzini@redhat.com \
--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 NNTP newsgroup(s).