From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Juergen Gross <jgross@suse.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: [patch 0/7] x86/KVM: Async #PF and instrumentation protection
Date: Tue, 19 May 2020 22:31:28 +0200 [thread overview]
Message-ID: <20200519203128.773151484@linutronix.de> (raw)
Folks,
this series is the KVM side of the ongoing quest to confine instrumentation
to safe places and ensure that RCU and context tracking state is correct.
The async #PF changes are in the tip tree already as they conflict with the
entry code rework. The minimal set of commits to carry these have been
isolated and tagged:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git noinstr-x86-kvm-2020-05-16
Paolo, please pull this into your next branch to avoid conflicts in
next. The prerequisites for the following KVM specific changes come with
that tag so that you have no merge dependencies.
The tag has also been merged into
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry
where the x86 core #PF entry code changes will be queued soon as well.
The KVM specific patches which deal with the RCU and context tracking state
and the protection against instrumentation in sensitive places have been
split out from the larger entry/noinstr series:
https://lore.kernel.org/r/20200505134112.272268764@linutronix.de
The patches deal with:
- Placing the guest_enter/exit() calls at the correct place
- Moving the sensitive VMENTER/EXIT code into the non-instrumentable code
section.
- Fixup the tracing code to comply with the non-instrumentation rules
- Use native functions to access CR2 and the GS base MSR in the critical
code pathes to prevent them from being instrumented.
The patches apply on top of
git://git.kernel.org/pub/scm/linux/kernel/git/kvm/kvm.git next
with the noinstr-x86-kvm-2020-05-16 tag from the tip tree merged in.
For reference the whole lot is available from:
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git kvm/noinstr
Thanks,
tglx
---
include/asm/hardirq.h | 4 +-
include/asm/kvm_host.h | 8 +++++
kvm/svm/svm.c | 65 ++++++++++++++++++++++++++++++++++------
kvm/svm/vmenter.S | 2 -
kvm/vmx/ops.h | 4 ++
kvm/vmx/vmenter.S | 5 ++-
kvm/vmx/vmx.c | 78 ++++++++++++++++++++++++++++++++++++++-----------
kvm/x86.c | 4 --
8 files changed, 137 insertions(+), 33 deletions(-)
next reply other threads:[~2020-05-19 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:31 Thomas Gleixner [this message]
2020-05-19 20:31 ` [patch 1/7] x86/kvm: Move context tracking where it belongs Thomas Gleixner
2020-05-19 20:31 ` [patch 2/7] x86/kvm/vmx: Add hardirq tracing to guest enter/exit Thomas Gleixner
2020-05-19 20:31 ` [patch 3/7] x86/kvm/svm: Add hardirq tracing on " Thomas Gleixner
2020-05-19 20:31 ` [patch 4/7] x86/kvm/vmx: Move guest enter/exit into .noinstr.text Thomas Gleixner
2020-05-19 20:31 ` [patch 5/7] x86/kvm/svm: " Thomas Gleixner
2020-05-19 20:31 ` [patch 6/7] x86/kvm/svm: Use uninstrumented wrmsrl() to restore GS Thomas Gleixner
2020-05-19 20:31 ` [patch 7/7] x86/kvm/vmx: Use native read/write_cr2() Thomas Gleixner
2020-05-20 7:41 ` [patch 0/7] x86/KVM: Async #PF and instrumentation protection Paolo Bonzini
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=20200519203128.773151484@linutronix.de \
--to=tglx@linutronix.de \
--cc=alexandre.chartre@oracle.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/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
Powered by JetHome