From: Pavan Kumar Paluri <papaluri@amd.com>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-doc@vger.kernel.org>, <linux-coco@lists.linux.dev>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Eric Van Tassell" <Eric.VanTassell@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Michael Roth <michael.roth@amd.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
"Pavan Kumar Paluri" <papaluri@amd.com>,
Dhaval Giani <dhaval.giani@amd.com>
Subject: [PATCH v6 0/2] nosnp sev command line support
Date: Thu, 10 Oct 2024 07:14:53 -0500 [thread overview]
Message-ID: <20241010121455.15795-1-papaluri@amd.com> (raw)
Provide "nosnp" boot option via "sev=nosnp" kernel command line to
prevent SEV-SNP [1] capable host kernel from enabling SEV-SNP and
initializing Reverse Map Table (RMP)
Setting 'nosnp' avoids the RMP check overhead in memory accesses when
users do not want to run SEV-SNP guests.
On providing sev=nosnp via kernel command line:
cat /sys/module/kvm_amd/parameters/sev_snp should be "N".
The patchset is based on tip/master.
Reference:
[1] https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/programmer-references/24593.pdf
Changelog:
=========
v5:
* Update cover-letter and Documentation to include information on why
nosnp command line option is required (Dave Hansen)
* Remove <asm/cache.h> stray header introduced in the previous
versions because of __read_mostly attribute that is now moved into
virt/svm/cmdline.c
* Link: https://lore.kernel.org/all/20240930231102.123403-1-papaluri@amd.com/
v4:
* Move __read_mostly attribute to place where sev_cfg is declared (Tom)
* Link: https://lore.kernel.org/all/20240922033626.29038-1-papaluri@amd.com/
Pavan Kumar Paluri (2):
x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm
x86 KVM:SVM: Provide "nosnp" boot option for sev kernel command line
.../arch/x86/x86_64/boot-options.rst | 5 +++
arch/x86/coco/sev/core.c | 44 -------------------
arch/x86/include/asm/sev-common.h | 27 ++++++++++++
arch/x86/virt/svm/Makefile | 1 +
arch/x86/virt/svm/cmdline.c | 39 ++++++++++++++++
5 files changed, 72 insertions(+), 44 deletions(-)
create mode 100644 arch/x86/virt/svm/cmdline.c
base-commit: 00d91979d23c88d3f50870e22fc9cec3f5e26a2a
--
2.34.1
next reply other threads:[~2024-10-10 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 12:14 Pavan Kumar Paluri [this message]
2024-10-10 12:14 ` [PATCH v6 1/2] x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm Pavan Kumar Paluri
2024-10-11 16:21 ` Borislav Petkov
2024-10-11 16:35 ` Tom Lendacky
2024-10-11 16:48 ` Borislav Petkov
2024-10-11 16:55 ` Tom Lendacky
2024-10-11 16:59 ` Borislav Petkov
2024-10-11 17:08 ` Paluri, PavanKumar
2024-10-11 22:16 ` Borislav Petkov
2024-10-10 12:14 ` [PATCH v6 2/2] x86 KVM:SVM: Provide "nosnp" boot option for sev kernel command line Pavan Kumar Paluri
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=20241010121455.15795-1-papaluri@amd.com \
--to=papaluri@amd.com \
--cc=Eric.VanTassell@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dhaval.giani@amd.com \
--cc=hpa@zytor.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
/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