From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
seanjc@google.com, peterz@infradead.org,
herbert@gondor.apana.org.au, davem@davemloft.net,
ardb@kernel.org
Cc: pbonzini@redhat.com, aik@amd.com, Michael.Roth@amd.com,
KPrateek.Nayak@amd.com, Tycho.Andersen@amd.com,
Nathan.Fontenot@amd.com, ackerleytng@google.com,
jackyli@google.com, pgonda@google.com, rientjes@google.com,
jacobhxu@google.com, xin@zytor.com,
pawan.kumar.gupta@linux.intel.com, babu.moger@amd.com,
dyoung@redhat.com, nikunj@amd.com, darwi@linutronix.de,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
kvm@vger.kernel.org, linux-coco@lists.linux.dev
Subject: Re: [PATCH 2/2] x86/sev: Only announce RMPOPT optimizations when SNP is enabled
Date: Wed, 14 Oct 2026 14:33:18 -0500 [thread overview]
Message-ID: <9f16cbfe-7864-4733-b4d3-4da03d731d7a@amd.com> (raw)
In-Reply-To: <a66f932d-4ca2-402d-9f76-628ef53a1107@amd.com>
On 10/14/2026 8:24 AM, Tom Lendacky wrote:
> On 10/13/26 10:44, Ashish Kalra wrote:
>> From: Ashish Kalra <ashish.kalra@amd.com>
>>
>> rmpopt_init() prints "RMPOPT optimizations enabled" gated only on
>> X86_FEATURE_RMPOPT, which is a CPUID bit advertised independently of
>> whether SNP is active. On a system where SNP is disabled in the BIOS the
>> message is still printed at boot even though RMPOPT is never actually used
>> (snp_enable_rmpopt() bails out on !CC_ATTR_HOST_SEV_SNP), which is
>> misleading.
>>
>> rmpopt_init() is only the software setup (workqueue and the delayed work);
>> the capability that matters for the message - an active SNP host - is
>> checked in snp_enable_rmpopt(). Move the announcement there, as a
>> pr_info_once(), so it is emitted only when RMPOPT is actually enabled on an
>> SNP host.
>>
>> Fixes: c6c6f156d192 ("x86/sev: Perform RMP optimizations asynchronously")
>> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
>> ---
>>
>> Note: in the posted series the pr_info_once() lived in
>> snp_enable_rmpopt() (SNP-gated); when applied, c6c6f156d192 moved it to
>> rmpopt_init() (feature-only-gated) as a plain pr_info(). This restores the
>> original placement.
>> arch/x86/virt/svm/sev.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/virt/svm/sev.c b/arch/x86/virt/svm/sev.c
>> index 43e4945e6cdf..6f5f4ee821d0 100644
>> --- a/arch/x86/virt/svm/sev.c
>> +++ b/arch/x86/virt/svm/sev.c
>> @@ -656,8 +656,6 @@ static int __init rmpopt_init(void)
>
> Should the check at the start of rmpopt_init() just be
>
> if (!cpu_feature_enabled(X86_FEATURE_SEV_SNP) ||
> !cpu_feature_enabled(X86_FEATURE_RMPOPT))
>
> so that you don't even bother setting up the workqueue, etc.?
>
Thanks, that's cleaner, and gating on X86_FEATURE_SEV_SNP avoids the workqueue setup entirely on a non-SNP host.
Will add this and post a v2, keeping the pr_info() in rmpopt_init().
Thanks,
Ashish
> Thanks,
> Tom
>
>> if ((rmpopt_pa_end - rmpopt_pa_start) > SZ_2T)
>> rmpopt_pa_end = rmpopt_pa_start + SZ_2T;
>>
>> - pr_info("RMPOPT optimizations enabled\n");
>> -
>> rmpopt_soft_init = true;
>>
>> return 0;
>> @@ -690,6 +688,8 @@ void snp_enable_rmpopt(void)
>>
>> mod_delayed_work(rmpopt_wq, &rmpopt_delayed_work,
>> msecs_to_jiffies(RMPOPT_WORK_TIMEOUT));
>> +
>> + pr_info_once("RMPOPT optimizations enabled\n");
>> }
>> EXPORT_SYMBOL_FOR_MODULES(snp_enable_rmpopt, "ccp,kvm-amd");
>>
>
prev parent reply other threads:[~2026-10-14 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 15:44 [PATCH 0/2] x86/sev: Fix RMPOPT enablement on non-RMPOPT configs Ashish Kalra
2026-10-13 15:44 ` [PATCH 1/2] x86/sev: Clear RMPOPT when segmented RMP is disabled by firmware Ashish Kalra
2026-10-13 22:26 ` Borislav Petkov
2026-10-13 23:24 ` Kalra, Ashish
2026-10-14 13:21 ` Tom Lendacky
2026-10-13 15:44 ` [PATCH 2/2] x86/sev: Only announce RMPOPT optimizations when SNP is enabled Ashish Kalra
2026-10-14 13:24 ` Tom Lendacky
2026-10-14 19:33 ` Kalra, Ashish [this message]
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=9f16cbfe-7864-4733-b4d3-4da03d731d7a@amd.com \
--to=ashish.kalra@amd.com \
--cc=KPrateek.Nayak@amd.com \
--cc=Michael.Roth@amd.com \
--cc=Nathan.Fontenot@amd.com \
--cc=Tycho.Andersen@amd.com \
--cc=ackerleytng@google.com \
--cc=aik@amd.com \
--cc=ardb@kernel.org \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dyoung@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jackyli@google.com \
--cc=jacobhxu@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=xin@zytor.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