From: "Paluri, PavanKumar" <papaluri@amd.com>
To: Dave Hansen <dave.hansen@intel.com>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.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>,
"Paluri, PavanKumar (Pavan Kumar)" <pavankumar.paluri@amd.com>
Subject: Re: [PATCH v5 0/2] nosnp sev command line support
Date: Mon, 30 Sep 2024 19:09:44 -0500 [thread overview]
Message-ID: <90493ac2-e1c5-f03e-9428-f6a147f37088@amd.com> (raw)
In-Reply-To: <f751ffe7-9900-4d91-9e7a-e560777725e1@intel.com>
Hello Dave,
On 9/30/2024 6:25 PM, Dave Hansen wrote:
> On 9/30/24 16:11, Pavan Kumar Paluri wrote:
>> 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) [1].
>>
>> On providing sev=nosnp via kernel command line:
>> cat /sys/module/kvm_amd/parameters/sev_snp should be "N".
>
> I don't see any mention in the changelog, cover letter or Documentation/
> about why someone would want to do this.
>
> I assume it's because of performance (walking the RMP table is non-zero
> cost).
>
> The BIOS allocates the RMP table, right? So this option presumably gets
> the performance back, but not the memory. That's probably also worth
> mentioning ... somewhere.
Yes, that is correct. RMP is BIOS-allocated, so there is a performance
gain but not memory.
Besides, having a 'nosnp' command line option would benefit customers to
be able to set the BIOS option to allocate RMP, but not actually enable
it just yet. This way, they can avoid overhead incurred from RMP checks,
for when they do not want to run SEV-SNP guests.
I will include this information in the cover-letter.
Thanks,
Pavan
next prev parent reply other threads:[~2024-10-01 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 23:11 Pavan Kumar Paluri
2024-09-30 23:11 ` [PATCH v5 1/2] x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm Pavan Kumar Paluri
2024-09-30 23:11 ` [PATCH v5 2/2] x86 KVM:SVM: Provide "nosnp" boot option for sev kernel command line Pavan Kumar Paluri
2024-09-30 23:25 ` [PATCH v5 0/2] nosnp sev command line support Dave Hansen
2024-10-01 0:09 ` Paluri, PavanKumar [this message]
2024-10-01 0:14 ` Dave Hansen
2024-10-01 0:18 ` Paluri, PavanKumar
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=90493ac2-e1c5-f03e-9428-f6a147f37088@amd.com \
--to=papaluri@amd.com \
--cc=Eric.VanTassell@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pavankumar.paluri@amd.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
all inboxes | Powered by JetHome®