From: Matthew Wilcox <willy@infradead.org>
To: Pavan Kumar Paluri <papaluri@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
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>,
Brijesh Singh <brijesh.singh@amd.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/2] "nosnp" sev command line support
Date: Thu, 1 Aug 2024 21:58:39 +0100 [thread overview]
Message-ID: <Zqv2_wQbCLN_AOfy@casper.infradead.org> (raw)
In-Reply-To: <20240801205638.6603-1-papaluri@amd.com>
On Thu, Aug 01, 2024 at 03:56:36PM -0500, Pavan Kumar Paluri wrote:
> Provide "nosnp" boot option via "sev=nosnp" kernel command line to
> prevent SNP-capable host kernel from enabling SEV-SNP and initializing
> RMP table.
Congratulations on using three acronyms multiple times and defining none
of them.
next prev parent reply other threads:[~2024-08-01 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 20:56 [PATCH 0/2] "nosnp" sev command line support Pavan Kumar Paluri
2024-08-01 20:56 ` [PATCH 1/2] x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm Pavan Kumar Paluri
2024-08-02 14:18 ` Tom Lendacky
2024-08-29 13:24 ` Borislav Petkov
2024-08-29 14:22 ` Borislav Petkov
2024-08-29 15:29 ` Paluri, PavanKumar
2024-08-29 15:41 ` Borislav Petkov
2024-08-29 15:53 ` Paluri, PavanKumar
2024-08-01 20:56 ` [PATCH 2/2] x86 KVM:SVM: Provide "nosnp" boot option for sev kernel command line Pavan Kumar Paluri
2024-08-02 14:19 ` Tom Lendacky
2024-08-01 20:58 ` Matthew Wilcox [this message]
2024-08-01 22:23 ` [PATCH 0/2] "nosnp" sev command line support Paluri, PavanKumar
2024-08-01 22:39 ` Matthew Wilcox
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=Zqv2_wQbCLN_AOfy@casper.infradead.org \
--to=willy@infradead.org \
--cc=Eric.VanTassell@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.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=papaluri@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