[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] x86: Fix AMD_SVM and INTEL_VMX dependency


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Orzel, Michal" <michal.orzel@xxxxxxx>
  • Date: Mon, 1 Sep 2025 13:25:12 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=suse.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=1lY+PfkKFnxrCbnL2IIXOubHGUZpoEuEuP7kTOb4ktw=; b=t9wH5y36+izy8TLN9gSfqh4YDcFYibkR5nnlfcXfrkUcfFj9bfyhEYCwu6QexEcUEyJObMfRTD9DW5tdxwTT6yGJZlVLWnZ5NmVx5c7+ipulP0Za1alz058NXZLz58CT9FNvwamdue2wnGG+46MQqakAHwm0G07+hq5oNexLKKukVlJGadgzFh8FFpFzs1H1zgDHSd5O0Pgwhc0UdKUkBRp+bcx7kiPIzW0G22Jsv6yba3wpo6/KItQQQPuQP8cp9RKMLHS/t3Trf8YbziJiUmpywBD0yv8RGAptHy+KqSeyVzLQvhwY34euSKL5qr2WWIgfCvetcSZp8qXaJTWJvw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=xSDrvNHkseGd5OgwAQaULKhskN+oALDUMws1Bry+7JRMGznF+Au8F/X3ye8vfBWcIxRDyZm+e1kGo/4LLBDFAOv1tq9DVNXGOMNWj1YPftxCimtE+woUKaM0zcUtTU1iDLqNKwhifmn65lvB9mwW0J7pc81AMAQJ0bbG8S2Gys6c0f1+sZCqhPyPoIlM3OcRmYv/nv50R3ONppHpw5Tx/doYId8SDAUSrlB3yrPUUebjjiXWEdSk60NJpCMeRM7Pu1cjgfNrLxS4meSVAJMmnCj+A9Z2E+z/EWkSux91SOvWJQqy7g2oLCTIh2O5qZEKIHSfVnPgGRJOKt6cwdLlOA==
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 01 Sep 2025 11:25:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 01/09/2025 13:19, Jan Beulich wrote:
> On 01.09.2025 12:43, Michal Orzel wrote:
>> Commit e3ed540f2e9f was meant to make AMD_SVM dependent on AMD and
>> INTEL_VMX on INTEL. Such dependency should be done using 'depends on'
>> and not 'if' next to prompt that deals only with the visibility of the
>> given Kconfig option. This makes it impossible to e.g. disable INTEL_VMX
>> when INTEL is disabled (option is hidden).
> 
> Hmm, yes, just that ...
> 
>> --- a/xen/arch/x86/hvm/Kconfig
>> +++ b/xen/arch/x86/hvm/Kconfig
>> @@ -16,7 +16,8 @@ menuconfig HVM
>>  if HVM
>>  
>>  config AMD_SVM
>> -    bool "AMD-V" if AMD && EXPERT
>> +    bool "AMD-V" if EXPERT
>> +    depends on AMD
>>      default y
>>      help
>>        Enables virtual machine extensions on platforms that implement the
>> @@ -25,7 +26,8 @@ config AMD_SVM
>>        If in doubt, say Y.
>>  
>>  config INTEL_VMX
>> -    bool "Intel VT-x" if INTEL && EXPERT
>> +    bool "Intel VT-x" if EXPERT
>> +    depends on INTEL
>>      default y
>>      select ARCH_VCPU_IOREQ_COMPLETION
>>      help
> 
> ... now it becomes impossible to _enable_ INTEL_VMX when INTEL is disabled,
> yet which may be of interest if you target some other vendor's VMX
> implementation. Perhaps really we should have
> 
> config INTEL_VMX
>       bool "Intel VT-x" if EXPERT
>       default INTEL
I did not think such configuration makes sense (VMX without INTEL)
which is in line with the last sentence from the mentioned commit.
I'm ok either way.

~Michal




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.