public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: pbonzini@redhat.com, seanjc@google.com, david.kaplan@amd.com,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: Disable AVIC on SNP-enabled system without HvInUseWrAllowed feature
Date: Fri, 18 Oct 2024 17:02:20 +0700	[thread overview]
Message-ID: <b79eb294-0c03-47d6-9117-3e76c4b73dad@amd.com> (raw)
In-Reply-To: <2d5f2f91-2c3a-4b0e-bacd-aeac6d4da724@oracle.com>

Hi Joao,

On 10/1/2024 6:04 PM, Joao Martins wrote:
> On 30/09/2024 06:50, Suravee Suthikulpanit wrote:
>> diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
>> index dd4682857c12..921b6de80e24 100644
>> --- a/arch/x86/include/asm/cpufeatures.h
>> +++ b/arch/x86/include/asm/cpufeatures.h
>> @@ -448,6 +448,7 @@
>>   #define X86_FEATURE_SME_COHERENT	(19*32+10) /* AMD hardware-enforced cache coherency */
>>   #define X86_FEATURE_DEBUG_SWAP		(19*32+14) /* "debug_swap" AMD SEV-ES full debug state swap support */
>>   #define X86_FEATURE_SVSM		(19*32+28) /* "svsm" SVSM present */
>> +#define X86_FEATURE_HV_INUSE_WR_ALLOWED	(19*32+30) /* Write to in-use hypervisor-owned pages allowed */
>>   
>>   /* AMD-defined Extended Feature 2 EAX, CPUID level 0x80000021 (EAX), word 20 */
>>   #define X86_FEATURE_NO_NESTED_DATA_BP	(20*32+ 0) /* No Nested Data Breakpoints */
>> diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c
>> index 4b74ea91f4e6..42f2caf17d6a 100644
>> --- a/arch/x86/kvm/svm/avic.c
>> +++ b/arch/x86/kvm/svm/avic.c
>> @@ -1199,6 +1199,12 @@ bool avic_hardware_setup(void)
>>   		return false;
>>   	}
>>   
>> +	if (cc_platform_has(CC_ATTR_HOST_SEV_SNP) &&
>> +	    !boot_cpu_has(X86_FEATURE_HV_INUSE_WR_ALLOWED)) {
>> +		pr_warn("AVIC disabled: missing HvInUseWrAllowed on SNP-enabled system");
>> +		return false;
>> +	}
>> +
> 
> Wouldn't be better to make this is APICv inhibit to allow non-SNP guests to work
> with AVIC?

I was considering the APICV inhibit as well, and decided to go with 
disabling AVIC since it does not require additional 
APICV_INHIBIT_REASON_XXX flag, and we can simply disable AVIC support 
during kvm-amd driver initialization.

After rethink this, it is better to use per-VM APICv inhibition instead 
since certain AVIC data structures will be needed for secure AVIC 
support in the future.

I will update this patch and send out V2.

Thanks,
Suravee

      reply	other threads:[~2024-10-18 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  5:50 [PATCH] KVM: SVM: Disable AVIC on SNP-enabled system without HvInUseWrAllowed feature Suravee Suthikulpanit
2024-09-30 16:04 ` Sean Christopherson
2024-10-01  8:59   ` Suthikulpanit, Suravee
2024-10-01 19:16     ` Sean Christopherson
2024-10-01 11:04 ` Joao Martins
2024-10-18 10:02   ` Suthikulpanit, Suravee [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=b79eb294-0c03-47d6-9117-3e76c4b73dad@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=david.kaplan@amd.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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