From: Alexey Kardashevskiy <aik@amd.com>
To: Alexey Kardashevskiy <aik@amd.com>
Cc: <kvm@vger.kernel.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>,
Venu Busireddy <venu.busireddy@oracle.com>,
Tony Luck <tony.luck@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sean Christopherson <seanjc@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael Sterritt <sterritt@google.com>,
Michael Roth <michael.roth@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Heiko Carstens <hca@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH kernel 0/3] KVM: SEV: Enable AMD SEV-ES DebugSwap
Date: Thu, 1 Dec 2022 13:19:45 +1100 [thread overview]
Message-ID: <20221201021948.9259-1-aik@amd.com> (raw)
This is to use another AMD SEV-ES hardware assisted register swap,
more detail in 2/3. The patches are fairly independend but required in
this order.
This is based on sha1 ef4d3ea40565 and requires something like this:
https://lkml.org/lkml/2022/11/29/1229
This patchset is pushed out at
https://github.com/aik/linux/commits/debugswap
Please comment. Thanks.
Alexey Kardashevskiy (3):
x86/amd/dr_addr_mask: Cache values in percpu variables
KVM: SEV: Enable DebugSwap
x86/sev: Do not handle #VC for DR7 read/write
arch/x86/include/asm/debugreg.h | 1 +
arch/x86/include/asm/svm.h | 1 +
arch/x86/kvm/svm/svm.h | 18 ++++++++---
arch/x86/kernel/cpu/amd.c | 32 ++++++++++++++++++++
arch/x86/kernel/sev.c | 6 ++++
arch/x86/kvm/svm/sev.c | 22 +++++++++++++-
arch/x86/kvm/svm/svm.c | 6 ++--
7 files changed, 78 insertions(+), 8 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-01 2:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 2:19 Alexey Kardashevskiy [this message]
2022-12-01 2:19 ` [PATCH kernel 1/3] x86/amd/dr_addr_mask: Cache values in percpu variables Alexey Kardashevskiy
2022-12-01 16:58 ` Sean Christopherson
2022-12-01 19:45 ` Andrew Cooper
2022-12-06 7:14 ` Alexey Kardashevskiy
2022-12-06 17:07 ` Sean Christopherson
2022-12-07 0:50 ` Alexey Kardashevskiy
2022-12-07 18:55 ` Borislav Petkov
2022-12-08 6:11 ` Alexey Kardashevskiy
2022-12-08 10:35 ` Borislav Petkov
2022-12-01 2:19 ` [PATCH kernel 2/3] KVM: SEV: Enable DebugSwap Alexey Kardashevskiy
2022-12-01 17:37 ` Sean Christopherson
2022-12-09 2:28 ` Alexey Kardashevskiy
2022-12-01 2:19 ` [PATCH kernel 3/3] x86/sev: Do not handle #VC for DR7 read/write Alexey Kardashevskiy
2022-12-01 17:38 ` Sean Christopherson
2022-12-07 19:01 ` Borislav Petkov
2022-12-07 19:07 ` Sean Christopherson
2022-12-08 7:14 ` Alexey Kardashevskiy
2022-12-08 11:01 ` Borislav Petkov
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=20221201021948.9259-1-aik@amd.com \
--to=aik@amd.com \
--cc=Jason@zx2c4.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=sterritt@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--cc=venu.busireddy@oracle.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;
as well as URLs for NNTP newsgroup(s).