KVM: x86: Add a new attribute to control dynamic XSTATE components
cover KVM: x86: Add a new attribute to control dynamic XSTATE components
Hi KVM folks,
While documenting the ARCH_{REQ|GET}_XCOMP_GUEST_PERM options [1], I came to think of this new attribute as it can provide more consistent way of enabling dynamic features for QEMU/KVM.
== Background ==
The new x86 arch_prctl() options [2] help to support dynamic AMX state enabling. As the VCPU permission should be separate, additional options are added for the userspace VMM like QEMU: ARCH_GET_XCOMP_GUEST_PERM and ARCH_REQ_XCOMP_GUEST_PERM.
== Problem ==
KVM has already established a set of ioctls to control VM attributes. It has the attribute to expose the KVM-supported XSTATE components [3]. This interface, however, is not necessarily compatible with those arch_prctl() options. KVM may choose and expose some of the host-supported features. Then using the host-provided interface may not comply with this KVM policy.
== Solution ==
The patchset adds a new attribute to control XSTATE permission:KVM_X86_XCOMP_GUEST_PERM, and it is available through the KVM_GET_DEVICE_ATTR/KVM_SET_DEVICE_ATTR APIs. The KVM AMX test is updated to use this. Then QEMU may switch to keep using the KVM API, which is more consistent.
[1]: https://lore.kernel.org/lkml/[email protected]/
[2]: https://docs.kernel.org/x86/xstate.html
[3]: https://gitlab.com/qemu-project/qemu/-/blob/master/linux-headers/asm-x86/kvm.h#L456
Chang S. Bae (2):
KVM: x86: Add a new system attribute for dynamic XSTATE component
selftests: kvm: Use the KVM API to enable dynamic XSTATE features
arch/x86/include/asm/fpu/api.h | 1 + arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/kernel/fpu/xstate.c | 6 ++++ arch/x86/kvm/x86.c | 31 +++++++++++++++++++ tools/arch/x86/include/uapi/asm/kvm.h | 1 + .../selftests/kvm/lib/x86_64/processor.c | 22 +++++++++---- 6 files changed, 56 insertions(+), 6 deletions(-)
base-commit: 1c23f9e627a7b412978b4e852793c5e3c3efc555
Signature · 1 line
2.17.1
RFC PATCH 1/2 KVM: x86: Add a new system attribute for dynamic XSTATE component
== Background ==
A set of architecture-specific prctl() options offer to control dynamic XSTATE components in VCPUs. Userspace VMMs may interact with the host using ARCH_GET_XCOMP_GUEST_PERM and ARCH_REQ_XCOMP_GUEST_PERM.
However, they are separated from the KVM API. KVM may select features that the host supports and advertise them through the KVM_X86_XCOMP_GUEST_SUPP attribute.
== Problem ==
QEMU [1] queries the features through the KVM API instead of using the x86 arch_prctl() option. But it still needs to use arch_prctl() to request the permission. Then this step may become fragile because it does not guarantee to comply with the KVM policy.
== Solution ==
Introduce a new attribute: KVM_X86_XCOMP_GUEST_PERM, and make it available via the KVM_GET_DEVICE_ATTR and KVM_SET_DEVICE_ATTR APIs.
The implementation needs to use the established fpu_xstate_prctl() extension for guest permissions. Export it via a new function xstate_req_guest_perm() that KVM may use.
[1] https://gitlab.com/qemu-project/qemu/-/commit/19db68ca68a7
--- arch/x86/include/asm/fpu/api.h | 1 + arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/kernel/fpu/xstate.c | 6 ++++++ arch/x86/kvm/x86.c | 31 +++++++++++++++++++++++++++++++ 4 files changed, 39 insertions(+)
arch/x86/include/asm/fpu/api.h +1 -0
@@ -133,6 +133,7 @@ static inline void fpstate_free(struct fpu *fpu) { }extern void fpstate_clear_xstate_component (struct fpstate *fps,unsigned int xfeature);extern u64 xstate_get_guest_group_perm (void ); +extern int xstate_req_guest_perm (unsigned long idx);/* KVM specific functions */ extern bool fpu_alloc_guest_fpstate (struct fpu_guest *gfpu);
arch/x86/include/uapi/asm/kvm.h +1 -0
@@ -461,6 +461,7 @@ struct kvm_sync_regs {/* attributes for system fd (group 0) */ #define KVM_X86_XCOMP_GUEST_SUPP 0 +#define KVM_X86_XCOMP_GUEST_PERM 1struct kvm_vmx_nested_state_data {__u8 vmcs12[KVM_STATE_NESTED_VMX_VMCS_SIZE ];
arch/x86/kernel/fpu/xstate.c +6 -0
@@ -1687,6 +1687,12 @@ u64 xstate_get_guest_group_perm(void) }EXPORT_SYMBOL_GPL (xstate_get_guest_group_perm); +int xstate_req_guest_perm (unsigned long idx) +{ +return xstate_request_perm (idx, true); +} +EXPORT_SYMBOL_GPL (xstate_req_guest_perm); +/** * fpu_xstate_prctl - xstate permission operations * @tsk: Redundant pointer to current
arch/x86/kvm/x86.c +31 -0
@@ -4514,12 +4514,34 @@ static int kvm_x86_dev_get_attr(struct kvm_device_attr *attr)if (put_user (kvm_caps.supported_xcr0, uaddr))return -EFAULT ;return 0 ; +case KVM_X86_XCOMP_GUEST_PERM : { +u64 permitted =xstate_get_guest_group_perm () & kvm_caps.supported_xcr0; + +return put_user (permitted, uaddr); + }default :return -ENXIO ;break ; } } +static int kvm_x86_dev_set_attr (struct kvm_device_attr *attr) +{ +unsigned long idx = (unsigned long )kvm_get_attr_addr (attr); + +if (attr->group) +return -ENXIO ; + +switch (attr->attr) { +case KVM_X86_XCOMP_GUEST_PERM : +if (!((1ULL << idx) & kvm_caps.supported_xcr0)) +return -EOPNOTSUPP ; +return xstate_req_guest_perm (idx); +default : +return -ENXIO ; + } +} +static int kvm_x86_dev_has_attr (struct kvm_device_attr *attr) {if (attr->group)
@@ -4629,6 +4651,15 @@ long kvm_arch_dev_ioctl(struct file *filp, r =kvm_x86_dev_get_attr (&attr);break ; } +case KVM_SET_DEVICE_ATTR : { +struct kvm_device_attr attr; + + r = -EFAULT ; +if (copy_from_user (&attr, (void __user *)arg,sizeof (attr))) +break ; + r =kvm_x86_dev_set_attr (&attr); +break ; + }case KVM_HAS_DEVICE_ATTR : {struct kvm_device_attr attr; r = -EFAULT ;
Signature · 1 line
2.17.1
Sean Christopherson
maintainerRe: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Quoted 10 lines · Chang S. Bae
== Background ==
A set of architecture-specific
prctl()options offer to control dynamic XSTATE components in VCPUs. Userspace VMMs may interact with the host usingARCH_GET_XCOMP_GUEST_PERMandARCH_REQ_XCOMP_GUEST_PERM.However, they are separated from the KVM API. KVM may select features that the host supports and advertise them through the
KVM_X86_XCOMP_GUEST_SUPPattribute.
Quoted 6 lines
== Problem ==
QEMU [1] queries the features through the KVM API instead of using the x86
arch_prctl()option. But it still needs to usearch_prctl()to request the permission. Then this step may become fragile because it does not guarantee to comply with the KVM policy.
But backdooring through KVM doesn't prevent usersepace from walking in through the front door (arch_prctl()), i.e. this doesn't protect the kernel in any way. KVM needs to ensure that _KVM_ doesn't screw up and let userspace use features that KVM doesn't support. The kernel's restrictions on using features goes on top, i.e. KVM must behave correctly irrespective of kernel restrictions.
If QEMU wants to assert that it didn't misconfigure itself, it can assert on the config in any number of ways, e.g. assert that ARCH_GET_XCOMP_GUEST_PERM is a subset of KVM_X86_XCOMP_GUEST_SUPP at the end of kvm_request_xsave_components().
Re: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Quoted 13 lines · Sean Christopherson
Quoted 12 lines · Chang S. Bae
== Background ==
A set of architecture-specific
prctl()options offer to control dynamic XSTATE components in VCPUs. Userspace VMMs may interact with the host usingARCH_GET_XCOMP_GUEST_PERMandARCH_REQ_XCOMP_GUEST_PERM.However, they are separated from the KVM API. KVM may select features that the host supports and advertise them through the
KVM_X86_XCOMP_GUEST_SUPPattribute.== Problem ==
Quoted 7 lines
Quoted 4 lines
QEMU [1] queries the features through the KVM API instead of using the x86
arch_prctl()option. But it still needs to usearch_prctl()to request the permission. Then this step may become fragile because it does not guarantee to comply with the KVM policy.But backdooring through KVM doesn't prevent usersepace from walking in through the front door (
arch_prctl()), i.e. this doesn't protect the kernel in any way.
No, I don't think backdooring is established in this proposal. The body of the arch_prctl() support is encapsulated inside of the x86 core code. KVM is simply calling it like arch_prctl() does.
Quoted 3 lines
KVM needs to ensure that _KVM_ doesn't screw up and let userspace use features that KVM doesn't support. The kernel's restrictions on using features goes on top, i.e. KVM must behave correctly irrespective of kernel restrictions.
Maybe this is a policy decision. I don't think that ARCH_REQ_XCOMP_GUEST_PERM goes away with this. Userspace may still use the arch_prctl() set. But then it makes more sense and consistent to use ARCH_GET_XCOMP_SUPP in first place, instead of KVM_X86_XCOMP_GUEST_SUPP, no?
Quoted 3 lines
If QEMU wants to assert that it didn't misconfigure itself, it can assert on the config in any number of ways, e.g. assert that
ARCH_GET_XCOMP_GUEST_PERMis a subset ofKVM_X86_XCOMP_GUEST_SUPPat the end ofkvm_request_xsave_components().
Yes, but I guess the new attribute can make it simple.
Thanks,
Chang
Sean Christopherson
maintainerRe: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Quoted 5 lines · Chang S. Bae
On 8/24/2022 2:42 PM, Sean Christopherson wrote:
Maybe this is a policy decision. I don't think thatARCH_REQ_XCOMP_GUEST_PERMgoes away with this. Userspace may still use thearch_prctl()set. But then it makes more sense and consistent to useARCH_GET_XCOMP_SUPPin first place, instead ofKVM_X86_XCOMP_GUEST_SUPP, no?
KVM_X86_XCOMP_GUEST_SUPP is needed so that userspace understands what _KVM_ supports.
Quoted 5 lines
Quoted 3 lines
If QEMU wants to assert that it didn't misconfigure itself, it can assert on the config in any number of ways, e.g. assert that
ARCH_GET_XCOMP_GUEST_PERMis a subset ofKVM_X86_XCOMP_GUEST_SUPPat the end ofkvm_request_xsave_components().Yes, but I guess the new attribute can make it simple.
Adding new uAPI and new exports to eliminate one line of userspace code is not a good tradeoff. Am I missing something? This really seems like solution looking for a problem.
Re: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Quoted 4 lines · Sean Christopherson
Adding new uAPI and new exports to eliminate one line of userspace code is not a good tradeoff. Am I missing something? This really seems like solution looking for a problem.
Well, then that's your call.
Yeah, that simplification is really minor. With this, I would rather think KVM wants enforcement before relaying the request to the host. That enforcement is unthinkable without supported_xcr0. But it looks like userspace is somehow trusted here for KVM.
Thanks,
Chang
Sean Christopherson
maintainerRe: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Quoted 11 lines · Chang S. Bae
Quoted 4 lines · Sean Christopherson
Adding new uAPI and new exports to eliminate one line of userspace code is not a good tradeoff. Am I missing something? This really seems like solution looking for a problem.
Well, then that's your call.
Yeah, that simplification is really minor. With this, I would rather think KVM wants enforcement before relaying the request to the host. That enforcement is unthinkable without
supported_xcr0.
My point is that KVM needs supported_xcr0 (or similar behavior) regardless of whether or not the kernel further restricts feature usage.
Quoted 1 line
But it looks like userspace is somehow trusted here for KVM.
RFC PATCH 2/2 selftests: kvm: Use the KVM API to enable dynamic XSTATE features
In reply to Chang S. BaeUse the KVM_X86_XCOMP_GUEST_PERM attribute, instead of the x86-specific prctl() options.
--- tools/arch/x86/include/uapi/asm/kvm.h | 1 + .../selftests/kvm/lib/x86_64/processor.c | 22 ++++++++++++++----- 2 files changed, 17 insertions(+), 6 deletions(-)
tools/arch/x86/include/uapi/asm/kvm.h +1 -0
@@ -461,6 +461,7 @@ struct kvm_sync_regs {/* attributes for system fd (group 0) */ #define KVM_X86_XCOMP_GUEST_SUPP 0 +#define KVM_X86_XCOMP_GUEST_PERM 1struct kvm_vmx_nested_state_data {__u8 vmcs12[KVM_STATE_NESTED_VMX_VMCS_SIZE ];
tools/testing/selftests/kvm/lib/x86_64/processor.c +16 -6
@@ -593,8 +593,6 @@ void __vm_xsave_require_permission(int bit, const char *name) kvm_fd =open_kvm_dev_path_or_exit (); rc =__kvm_ioctl (kvm_fd,KVM_GET_DEVICE_ATTR , &attr); -close (kvm_fd); -if (rc ==-1 && (errno ==ENXIO || errno ==EINVAL ))__TEST_REQUIRE (0 ,"KVM_X86_XCOMP_GUEST_SUPP not supported" );
@@ -603,13 +601,25 @@ void __vm_xsave_require_permission(int bit, const char *name)__TEST_REQUIRE (bitmask & (1ULL << bit),"Required XSAVE feature '%s' not supported" , name); -TEST_REQUIRE (!syscall (SYS_arch_prctl,ARCH_REQ_XCOMP_GUEST_PERM , bit)); + attr.attr =KVM_X86_XCOMP_GUEST_PERM ; + attr.addr = (unsigned long ) bit; + rc =__kvm_ioctl (kvm_fd,KVM_SET_DEVICE_ATTR , &attr); +if (rc ==-1 && (errno ==ENXIO || errno ==EINVAL )) +__TEST_REQUIRE (0 ,"KVM_X86_XCOMP_GUEST_PERM not supported" ); - rc =syscall (SYS_arch_prctl,ARCH_GET_XCOMP_GUEST_PERM , &bitmask); -TEST_ASSERT (rc ==0 ,"prctl(ARCH_GET_XCOMP_GUEST_PERM) error: %ld" , rc); +TEST_ASSERT (rc ==0 ,"KVM_SET_DEVICE_ATTR(0, KVM_X86_XCOMP_GUEST_PERM) error: %ld" , rc); + + attr.addr = (unsigned long ) &bitmask; + rc =__kvm_ioctl (kvm_fd,KVM_GET_DEVICE_ATTR , &attr); +if (rc ==-1 && (errno ==ENXIO || errno ==EINVAL )) +__TEST_REQUIRE (0 ,"KVM_X86_XCOMP_GUEST_PERM not supported" ); + +TEST_ASSERT (rc ==0 ,"KVM_GET_DEVICE_ATTR(0, KVM_X86_XCOMP_GUEST_PERM) error: %ld" , rc);TEST_ASSERT (bitmask & (1ULL << bit), -"prctl(ARCH_REQ_XCOMP_GUEST_PERM) failure bitmask=0x%lx" , +"KVM_GET_DEVICE_ATTR(0, KVM_X86_XCOMP_GUEST_PERM) failure bitmask=0x%lx" , bitmask); + +close (kvm_fd); } struct kvm_vcpu *vm_arch_vcpu_add(struct kvm_vm *vm, uint32_t vcpu_id,
Signature · 1 line
2.17.1