From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Borislav Petkov <bp@alien8.de>, Tom Lendacky <thomas.lendacky@amd.com>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
tglx@kernel.org, mingo@redhat.com, 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, pbonzini@redhat.com,
aik@amd.com, Michael.Roth@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 v4 1/2] x86/sev: Clear RMPOPT when segmented RMP is disabled by firmware
Date: Mon, 2 Nov 2026 18:07:35 -0600 [thread overview]
Message-ID: <30947e17-bffc-4c70-b19c-56504771c9fa@amd.com> (raw)
In-Reply-To: <20261102214343.GFaukED8ep3EMmQxfx@fat_crate.local>
On 11/2/2026 3:43 PM, Borislav Petkov wrote:
> On Mon, Nov 02, 2026 at 03:25:52PM -0600, Tom Lendacky wrote:
>> The current code clears X86_FEATURE_RMPOPT when
>> probe_segmented_rmptable_info() fails. The above code doesn't.
>
> See the hunk in cpuid-deps.c
>
>> But since SNP will be disabled on failure of snp_probe_rmptable_info(),
>> I guess it doesn't matter. In which case you can eliminate the goto by
>> doing:
>
>>
>> if (cpu_feature_enabled(X86_FEATURE_SEGMENTED_RMP)) {
>> rdmsrq(MSR_AMD64_RMP_CFG, rmp_cfg);
>> if (rmp_cfg & MSR_AMD64_SEG_RMP_ENABLED)
>> return probe_segmented_rmptable_info();
>> }
>>
>> setup_clear_cpu_cap(X86_FEATURE_RMPOPT);
>> return probe_contiguous_rmptable_info();
>>
>> Which looks pretty clean.
>
> Yap.
LGTM, tested on HW.
Thanks,
Ashish
>
>>> diff --git a/arch/x86/kernel/cpu/cpuid-deps.c b/arch/x86/kernel/cpu/cpuid-deps.c
>>> index 99801e844b30..acbcec394ef1 100644
>>> --- a/arch/x86/kernel/cpu/cpuid-deps.c
>>> +++ b/arch/x86/kernel/cpu/cpuid-deps.c
>>> @@ -93,6 +93,7 @@ static const struct cpuid_dep cpuid_deps[] = {
>>> { X86_FEATURE_SPEC_CTRL_SSBD, X86_FEATURE_SPEC_CTRL },
>>> { X86_FEATURE_LASS, X86_FEATURE_SMAP },
>>> { X86_FEATURE_INVLPGB, X86_FEATURE_PCID },
>>> + { X86_FEATURE_RMPOPT, X86_FEATURE_SEV_SNP },
>
> This hunk.
>
next prev parent reply other threads:[~2026-11-03 0:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 19:48 [PATCH v4 0/2] x86/sev: Fix RMPOPT enablement on non-RMPOPT configs Ashish Kalra
2026-10-28 19:49 ` [PATCH v4 1/2] x86/sev: Clear RMPOPT when segmented RMP is disabled by firmware Ashish Kalra
2026-10-28 21:51 ` Pankaj Gupta
2026-11-02 5:28 ` Borislav Petkov
2026-11-02 6:12 ` K Prateek Nayak
2026-11-02 7:01 ` Borislav Petkov
2026-11-02 14:12 ` Tom Lendacky
2026-11-02 14:48 ` Borislav Petkov
2026-11-02 15:50 ` Kalra, Ashish
2026-11-02 19:31 ` Borislav Petkov
2026-11-02 20:21 ` Kalra, Ashish
2026-11-03 0:22 ` Borislav Petkov
2026-11-02 21:25 ` Tom Lendacky
2026-11-02 21:43 ` Borislav Petkov
2026-11-03 0:07 ` Kalra, Ashish [this message]
2026-11-03 0:45 ` Borislav Petkov
2026-11-03 2:58 ` K Prateek Nayak
2026-10-28 19:49 ` [PATCH v4 2/2] x86/sev: Set up RMPOPT only on an active SNP host Ashish Kalra
2026-10-28 22:00 ` Gupta, Pankaj
2026-10-29 15:33 ` Tom Lendacky
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=30947e17-bffc-4c70-b19c-56504771c9fa@amd.com \
--to=ashish.kalra@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=kprateek.nayak@amd.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
all inboxes | Powered by JetHome®