From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/sev for v5.14
Date: Mon, 28 Jun 2021 10:39:38 +0200 [thread overview]
Message-ID: <YNmKyjD8UH6ETawm@zn.tnic> (raw)
Hi Linus,
please pull the current pile of enhancements and fixes to the SEV side
of things, for v5.14.
Thx.
---
The following changes since commit 614124bea77e452aa6df7a8714e8bc820b489922:
Linux 5.13-rc5 (2021-06-06 15:47:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_sev_for_v5.14_rc1
for you to fetch changes up to 8d9d46bbf3b6b7ff8edcac33603ab45c29e0e07f:
x86/sev: Use "SEV: " prefix for messages from sev.c (2021-06-23 11:56:18 +0200)
----------------------------------------------------------------
- Differentiate the type of exception the #VC handler raises depending
on code executed in the guest and handle the case where failure to
get the RIP would result in a #GP, as it should, instead of in a #PF
- Disable interrupts while the per-CPU GHCB is held
- Split the #VC handler depending on where the #VC exception has
happened and therefore provide for precise context tracking like the
rest of the exception handlers deal with noinstr regions now
- Add defines for the GHCB version 2 protocol so that further shared
development with KVM can happen without merge conflicts
- The usual small cleanups
----------------------------------------------------------------
Brijesh Singh (1):
x86/sev: Add defines for GHCB version 2 MSR protocol requests
Joerg Roedel (7):
x86/sev: Fix error message in runtime #VC handler
x86/insn-eval: Make 0 a valid RIP for insn_get_effective_ip()
x86/insn: Extend error reporting from insn_fetch_from_user[_inatomic]()
x86/sev: Propagate #GP if getting linear instruction address failed
x86/sev: Make sure IRQs are disabled while GHCB is active
x86/sev: Split up runtime #VC handler for correct state tracking
x86/sev: Use "SEV: " prefix for messages from sev.c
arch/x86/entry/entry_64.S | 4 +-
arch/x86/include/asm/idtentry.h | 29 ++----
arch/x86/include/asm/sev-common.h | 16 ++-
arch/x86/kernel/sev.c | 201 +++++++++++++++++++++-----------------
arch/x86/kernel/umip.c | 10 +-
arch/x86/lib/insn-eval.c | 30 +++---
6 files changed, 160 insertions(+), 130 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-06-28 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 8:39 Borislav Petkov [this message]
2021-06-28 18:34 ` pr-tracker-bot
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=YNmKyjD8UH6ETawm@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®