x86/sgx: Declare sgx_set_attribute() for !CONFIG_X86_SGX
Jarkko Sakkinen
maintainerPATCH 1/1 x86/sgx: Declare sgx_set_attribute() for !CONFIG_X86_SGX
Simplify sgx_set_attribute() usage by declaring a fallback implementation for it rather than requiring to have compilation flag checks in the call site. The fallback unconditionally returns -EINVAL.
Refactor the call site in kvm_vm_ioctl_enable_cap() accordingly. The net result is the same: KVM_CAP_SGX_ATTRIBUTE causes -EINVAL when kernel is compiled without CONFIG_X86_SGX_KVM.
--- arch/x86/include/asm/sgx.h | 8 ++++++++ arch/x86/kvm/x86.c | 2 -- 2 files changed, 8 insertions(+), 2 deletions(-)
arch/x86/include/asm/sgx.h +8 -0
@@ -372,7 +372,15 @@ int sgx_virt_einit(void __user *sigstruct, void __user *token, void __user *secs, u64 *lepubkeyhash, int *trapnr);#endif +#ifdef CONFIG_X86_SGX int sgx_set_attribute (unsigned long *allowed_attributes,unsigned int attribute_fd); +#else +static inline int sgx_set_attribute (unsigned long *allowed_attributes, +unsigned int attribute_fd) +{ +return -EINVAL ; +} +#endif #endif /* _ASM_X86_SGX_H */
arch/x86/kvm/x86.c +0 -2
@@ -5633,7 +5633,6 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm, kvm->arch.bus_lock_detection_enabled = true; r =0 ;break ; -#ifdef CONFIG_X86_SGX_KVM case KVM_CAP_SGX_ATTRIBUTE : {unsigned long allowed_attributes =0 ;
@@ -5649,7 +5648,6 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm, r = -EINVAL ;break ; } -#endif case KVM_CAP_VM_COPY_ENC_CONTEXT_FROM : r = -EINVAL ;if (kvm_x86_ops.vm_copy_enc_context_from)
Signature · 1 line
2.25.1
Sean Christopherson
maintainerQuoted 8 lines · Jarkko Sakkinen
Simplify
sgx_set_attribute()usage by declaring a fallback implementation for it rather than requiring to have compilation flag checks in the call site. The fallback unconditionally returns-EINVAL.Refactor the call site in
kvm_vm_ioctl_enable_cap()accordingly. The net result is the same:KVM_CAP_SGX_ATTRIBUTEcauses-EINVALwhen kernel is compiled withoutCONFIG_X86_SGX_KVM.
Eh, it doesn't really simplify the usage. If anything it makes it more convoluted because the capability check in kvm_vm_ioctl_check_extension() still needs an #ifdef, e.g. readers will wonder why the check is conditional but the usage is not.
Quoted 50 lines
Cc Tony Luck <[email protected]>Signed-off-by Jarkko Sakkinen <[email protected]>--- arch/x86/include/asm/sgx.h | 8 ++++++++ arch/x86/kvm/x86.c | 2 -- 2 files changed, 8 insertions(+), 2 deletions(-)arch/x86/include/asm/sgx.h +8
-0@@ -372,7 +372,15 @@ int sgx_virt_einit(void __user *sigstruct, void __user *token, void __user *secs, u64 *lepubkeyhash, int *trapnr);#endif +#ifdef CONFIG_X86_SGX int sgx_set_attribute (unsigned long *allowed_attributes,unsigned int attribute_fd); +#else +static inline int sgx_set_attribute (unsigned long *allowed_attributes, +unsigned int attribute_fd) +{ +return -EINVAL ; +} +#endif #endif /* _ASM_X86_SGX_H */ arch/x86/kvm/x86.c +0
-2@@ -5633,7 +5633,6 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm, kvm->arch.bus_lock_detection_enabled = true; r =0 ;break ; -#ifdef CONFIG_X86_SGX_KVM case KVM_CAP_SGX_ATTRIBUTE : {unsigned long allowed_attributes =0 ;@@ -5649,7 +5648,6 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm, r = -EINVAL ;break ; } -#endif case KVM_CAP_VM_COPY_ENC_CONTEXT_FROM : r = -EINVAL ;if (kvm_x86_ops.vm_copy_enc_context_from)Signature · 1 line
2.25.1
Jarkko Sakkinen
maintainerQuoted 6 lines · Sean Christopherson
Quoted 5 lines · Jarkko Sakkinen
Simplify
sgx_set_attribute()usage by declaring a fallback implementation for it rather than requiring to have compilation flag checks in the call site. The fallback unconditionally returns-EINVAL.
Quoted 7 lines
Quoted 3 lines
Refactor the call site in
kvm_vm_ioctl_enable_cap()accordingly. The net result is the same:KVM_CAP_SGX_ATTRIBUTEcauses-EINVALwhen kernel is compiled withoutCONFIG_X86_SGX_KVM.Eh, it doesn't really simplify the usage. If anything it makes it more convoluted because the capability check in
kvm_vm_ioctl_check_extension()still needs an #ifdef, e.g. readers will wonder why the check is conditional but the usage is not.
It does objectively a bit, since it's one ifdef less.
This is fairly standard practice to do in kernel APIs, used in countless places, for instance in Tony's patch set to add MCE recovery for SGX. And it would be nice to share common pattern here how we define API now and futre.
I also remarked that declaration of "sgx_provisioning_allowed" is not flagged, which is IMHO even more convolved because without SGX it is spare data.
/Jarkko
Jarkko Sakkinen
maintainerQuoted 17 lines · Jarkko Sakkinen
Quoted 6 lines · Sean Christopherson
Quoted 5 lines · Jarkko Sakkinen
Simplify
sgx_set_attribute()usage by declaring a fallback implementation for it rather than requiring to have compilation flag checks in the call site. The fallback unconditionally returns-EINVAL.Quoted 7 lines
Quoted 3 lines
Refactor the call site in
kvm_vm_ioctl_enable_cap()accordingly. The net result is the same:KVM_CAP_SGX_ATTRIBUTEcauses-EINVALwhen kernel is compiled withoutCONFIG_X86_SGX_KVM.Eh, it doesn't really simplify the usage. If anything it makes it more convoluted because the capability check in
kvm_vm_ioctl_check_extension()still needs an #ifdef, e.g. readers will wonder why the check is conditional but the usage is not.It does objectively a bit, since it's one ifdef less.
Quoted 7 lines
This is fairly standard practice to do in kernel APIs, used in countless places, for instance in Tony's patch set to add MCE recovery for SGX. And it would be nice to share common pattern here how we define API now and futre.
I also remarked that declaration of "
sgx_provisioning_allowed" is not flagged, which is IMHO even more convolved because without SGX it is spare data.
This should have had RFC tho (my bad forgot --subject-prefix="PATCH RFC"), given that this makes less sense alone than within context of patch set. I get that like this it's not worth of applying even if it makes sense as a change.
I prefer sending patches, rather than attaching patches to responses, because:
1. They get a lore.kernel.org link.
2. Can be fluently applied to other patch sets with b4:
https://people.kernel.org/monsieuricon/introducing-4-and-patch-attestation
3. They get a patchwork link.
Attachments are not as nice objects to manage as distinct emails.
/Jarkko
Paolo Bonzini
maintainerQuoted 4 lines · Jarkko Sakkinen
Quoted 3 lines
Eh, it doesn't really simplify the usage. If anything it makes it more convoluted because the capability check in
kvm_vm_ioctl_check_extension()still needs an #ifdef, e.g. readers will wonder why the check is conditional but the usage is not.It does objectively a bit, since it's one ifdef less.
But you're effectively replacing #ifdef CONFIG_X86_SGX_KVM with #ifdef CONFIG_X86_SGX; so the patch is not a no-op as far as KVM is concerned.
So NACK for the KVM parts (yeah I know it's RFC but just to be clearer), but I agree that adding a stub inline version of the function is standard practice and we do it a lot in KVM too.
Paolo
Quoted 7 lines
This is fairly standard practice to do in kernel APIs, used in countless places, for instance in Tony's patch set to add MCE recovery for SGX. And it would be nice to share common pattern here how we define API now and futre.
I also remarked that declaration of "
sgx_provisioning_allowed" is not flagged, which is IMHO even more convolved because without SGX it is spare data.
Jarkko Sakkinen
maintainerQuoted 4 lines · Paolo Bonzini
Quoted 3 lines · Jarkko Sakkinen
Quoted 3 lines
Eh, it doesn't really simplify the usage. If anything it makes it more convoluted because the capability check in
kvm_vm_ioctl_check_extension()still needs an #ifdef, e.g. readers will wonder why the check is conditional but the usage is not.
Quoted 8 lines
Quoted 1 line
It does objectively a bit, since it's one ifdef less.
But you're effectively replacing #ifdef
CONFIG_X86_SGX_KVMwith #ifdefCONFIG_X86_SGX; so the patch is not a no-op as far as KVM is concerned.So NACK for the KVM parts (yeah I know it's RFC but just to be clearer), but I agree that adding a stub inline version of the function is standard practice and we do it a lot in KVM too.
OK, this is perfectly fine for me (I care most that we can do this in SGX side).
/Jarkko