From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, herbert@gondor.apana.org.au
Cc: x86@kernel.org, john.allen@amd.com, davem@davemloft.net,
michael.roth@amd.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v4 4/5] KVM: SEV: Introduce new min,max sev_es and sev_snp asid variables
Date: Wed, 4 Jun 2025 18:12:23 -0500 [thread overview]
Message-ID: <f4f9a3cb-eb8e-4d7d-8fe1-5cceca5507c6@amd.com> (raw)
In-Reply-To: <1905a57f-3a0b-7106-111a-8231a6ec9380@amd.com>
On 6/3/2025 10:52 AM, Tom Lendacky wrote:
> On 5/19/25 18:57, Ashish Kalra wrote:
>> From: Ashish Kalra <ashish.kalra@amd.com>
>>
>> Introduce new min, max sev_es_asid and sev_snp_asid variables.
>>
>> The new {min,max}_{sev_es,snp}_asid variables along with existing
>> {min,max}_sev_asid variable simplifies partitioning of the
>> SEV and SEV-ES+ ASID space.
>>
>> Suggested-by: Sean Christopherson <seanjc@google.com>
>> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
>> ---
>> arch/x86/kvm/svm/sev.c | 37 ++++++++++++++++++++++++++++---------
>> 1 file changed, 28 insertions(+), 9 deletions(-)
>>
>> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
>> index dea9480b9ff6..383db1da8699 100644
>> --- a/arch/x86/kvm/svm/sev.c
>> +++ b/arch/x86/kvm/svm/sev.c
>> @@ -85,6 +85,10 @@ static DECLARE_RWSEM(sev_deactivate_lock);
>> static DEFINE_MUTEX(sev_bitmap_lock);
>> unsigned int max_sev_asid;
>> static unsigned int min_sev_asid;
>> +static unsigned int max_sev_es_asid;
>> +static unsigned int min_sev_es_asid;
>> +static unsigned int max_snp_asid;
>> +static unsigned int min_snp_asid;
>> static unsigned long sev_me_mask;
>> static unsigned int nr_asids;
>> static unsigned long *sev_asid_bitmap;
>> @@ -172,20 +176,32 @@ static void sev_misc_cg_uncharge(struct kvm_sev_info *sev)
>> misc_cg_uncharge(type, sev->misc_cg, 1);
>> }
>>
>> -static int sev_asid_new(struct kvm_sev_info *sev)
>> +static int sev_asid_new(struct kvm_sev_info *sev, unsigned long vm_type)
>> {
>> /*
>> * SEV-enabled guests must use asid from min_sev_asid to max_sev_asid.
>> * SEV-ES-enabled guest can use from 1 to min_sev_asid - 1.
>> - * Note: min ASID can end up larger than the max if basic SEV support is
>> - * effectively disabled by disallowing use of ASIDs for SEV guests.
>> */
>> - unsigned int min_asid = sev->es_active ? 1 : min_sev_asid;
>> - unsigned int max_asid = sev->es_active ? min_sev_asid - 1 : max_sev_asid;
>> - unsigned int asid;
>> + unsigned int min_asid, max_asid, asid;
>> bool retry = true;
>> int ret;
>>
>> + if (vm_type == KVM_X86_SNP_VM) {
>> + min_asid = min_snp_asid;
>> + max_asid = max_snp_asid;
>> + } else if (sev->es_active) {
>> + min_asid = min_sev_es_asid;
>> + max_asid = max_sev_es_asid;
>> + } else {
>> + min_asid = min_sev_asid;
>> + max_asid = max_sev_asid;
>> + }
>> +
>> + /*
>> + * The min ASID can end up larger than the max if basic SEV support is
>> + * effectively disabled by disallowing use of ASIDs for SEV guests.
>> + */
>> +
>
> Remove blank line.
>
>> if (min_asid > max_asid)
>> return -ENOTTY;
>>
>> @@ -439,7 +455,7 @@ static int __sev_guest_init(struct kvm *kvm, struct kvm_sev_cmd *argp,
>> if (vm_type == KVM_X86_SNP_VM)
>> sev->vmsa_features |= SVM_SEV_FEAT_SNP_ACTIVE;
>>
>> - ret = sev_asid_new(sev);
>> + ret = sev_asid_new(sev, vm_type);
>> if (ret)
>> goto e_no_asid;
>>
>> @@ -3029,6 +3045,9 @@ void __init sev_hardware_setup(void)
>> goto out;
>> }
>>
>> + min_sev_es_asid = min_snp_asid = 1;
>> + max_sev_es_asid = max_snp_asid = min_sev_asid - 1;
>
> Should these be moved to after the min_sev_asid == 1 check ...
>
>> +
>> /* Has the system been allocated ASIDs for SEV-ES? */
>> if (min_sev_asid == 1)
>> goto out;
>> @@ -3048,11 +3067,11 @@ void __init sev_hardware_setup(void)
>> if (boot_cpu_has(X86_FEATURE_SEV_ES))
>> pr_info("SEV-ES %s (ASIDs %u - %u)\n",
>> str_enabled_disabled(sev_es_supported),
>> - min_sev_asid > 1 ? 1 : 0, min_sev_asid - 1);
>> + min_sev_es_asid, max_sev_es_asid);
>
> ... so that this becomes 0 and 0 if min_sev_asid == 1 ? (like before)
>
>> if (boot_cpu_has(X86_FEATURE_SEV_SNP))
>> pr_info("SEV-SNP %s (ASIDs %u - %u)\n",
>> str_enabled_disabled(sev_snp_supported),
>> - min_sev_asid > 1 ? 1 : 0, min_sev_asid - 1);
>> + min_snp_asid, max_snp_asid);
>
> Ditto
>
Yes that makes sense.
Thanks,
Ashish
> Thanks,
> Tom
>
>> > sev_enabled = sev_supported;
>> sev_es_enabled = sev_es_supported;
next prev parent reply other threads:[~2025-06-04 23:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 23:56 [PATCH v4 0/5] Add SEV-SNP CipherTextHiding feature support Ashish Kalra
2025-05-19 23:56 ` [PATCH v4 1/5] crypto: ccp: New bit-field definitions for SNP_PLATFORM_STATUS command Ashish Kalra
2025-06-03 14:03 ` Tom Lendacky
2025-05-19 23:56 ` [PATCH v4 2/5] crypto: ccp: Add support for SNP_FEATURE_INFO command Ashish Kalra
2025-06-03 15:21 ` Tom Lendacky
2025-06-04 22:52 ` Kalra, Ashish
2025-06-05 15:51 ` Tom Lendacky
2025-06-05 4:49 ` Alexey Kardashevskiy
2025-06-05 19:34 ` Kalra, Ashish
2025-05-19 23:57 ` [PATCH v4 3/5] crypto: ccp: Add support to enable CipherTextHiding on SNP_INIT_EX Ashish Kalra
2025-06-03 15:41 ` Tom Lendacky
2025-06-04 22:55 ` Kalra, Ashish
2025-06-05 6:32 ` Alexey Kardashevskiy
2025-06-05 19:09 ` Kalra, Ashish
2025-05-19 23:57 ` [PATCH v4 4/5] KVM: SEV: Introduce new min,max sev_es and sev_snp asid variables Ashish Kalra
2025-06-03 15:52 ` Tom Lendacky
2025-06-04 23:12 ` Kalra, Ashish [this message]
2025-05-20 0:02 ` [PATCH v4 5/5] KVM: SEV: Add SEV-SNP CipherTextHiding support Ashish Kalra
2025-05-23 17:29 ` Dave Hansen
2025-06-02 20:32 ` Kalra, Ashish
2025-06-03 16:26 ` Tom Lendacky
2025-06-05 0:17 ` Kalra, Ashish
2025-06-05 16:23 ` Tom Lendacky
2025-06-05 19:21 ` Kalra, Ashish
2025-06-05 6:32 ` Alexey Kardashevskiy
2025-06-05 19:18 ` Kalra, Ashish
2025-05-22 14:56 ` [PATCH v4 0/5] Add SEV-SNP CipherTextHiding feature support Kim Phillips
2025-05-27 20:47 ` Kalra, Ashish
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=f4f9a3cb-eb8e-4d7d-8fe1-5cceca5507c6@amd.com \
--to=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=john.allen@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/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®