On Wednesday, January 12, 2022 10:51 AM, Zeng, Guang wrote:
> To: Tian, Kevin ; Zhong, Yang ;
> qemu-devel@nongnu.org
> Cc: pbonz...@redhat.com; Christopherson,, Sean ;
> jing2@linux.intel.com; Wang, Wei W
> Subject: Re: [RFC PATCH 6/7] x86: Use new XSAVE ioctls handling
>
On 1/11/2022 10:30 AM, Tian, Kevin wrote:
From: Zeng, Guang
Sent: Monday, January 10, 2022 5:47 PM
On 1/10/2022 4:40 PM, Tian, Kevin wrote:
From: Zhong, Yang
Sent: Friday, January 7, 2022 5:32 PM
From: Jing Liu
Extended feature has large state while current
kvm_xsave only allows 4KB. Use
On 1/11/2022 10:30 AM, Tian, Kevin wrote:
From: Zeng, Guang
Sent: Monday, January 10, 2022 5:47 PM
On 1/10/2022 4:40 PM, Tian, Kevin wrote:
From: Zhong, Yang
Sent: Friday, January 7, 2022 5:32 PM
From: Jing Liu
Extended feature has large state while current
kvm_xsave only allows 4KB. Use
> From: Zeng, Guang
> Sent: Monday, January 10, 2022 5:47 PM
>
> On 1/10/2022 4:40 PM, Tian, Kevin wrote:
> >> From: Zhong, Yang
> >> Sent: Friday, January 7, 2022 5:32 PM
> >>
> >> From: Jing Liu
> >>
> >> Extended feature has large state while current
> >> kvm_xsave only allows 4KB. Use new
On 1/10/2022 4:40 PM, Tian, Kevin wrote:
From: Zhong, Yang
Sent: Friday, January 7, 2022 5:32 PM
From: Jing Liu
Extended feature has large state while current
kvm_xsave only allows 4KB. Use new XSAVE ioctls
if the xstate size is large than kvm_xsave.
shouldn't we always use the new xsave
> From: Zhong, Yang
> Sent: Friday, January 7, 2022 5:32 PM
>
> From: Jing Liu
>
> Extended feature has large state while current
> kvm_xsave only allows 4KB. Use new XSAVE ioctls
> if the xstate size is large than kvm_xsave.
shouldn't we always use the new xsave ioctls as long as
CAP_XSAVE2
From: Jing Liu
Extended feature has large state while current
kvm_xsave only allows 4KB. Use new XSAVE ioctls
if the xstate size is large than kvm_xsave.
Signed-off-by: Jing Liu
Signed-off-by: Zeng Guang
Signed-off-by: Wei Wang
Signed-off-by: Yang Zhong
---
linux-headers/asm-x86/kvm.h | 14
