[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <624e948558c013904695cb66af6f299890e3612a.camel@intel.com>
Date: Thu, 30 Nov 2023 18:02:44 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Yang, Weijiang" <weijiang.yang@...el.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mlevitsk@...hat.com" <mlevitsk@...hat.com>
CC: "peterz@...radead.org" <peterz@...radead.org>,
"john.allen@....com" <john.allen@....com>,
"Gao, Chao" <chao.gao@...el.com>
Subject: Re: [PATCH v7 05/26] x86/fpu/xstate: Introduce fpu_guest_cfg for
guest FPU configuration
On Thu, 2023-11-30 at 19:29 +0200, Maxim Levitsky wrote:
> 2. It will affect output size of the KVM_GET_XSAVE2 ioctl, which
> outputs buffer similar to
> other FPU state buffers exposed to userspace (like one saved on
> signal stack, or one obtained via ptrace).
Ah! I missed this part. Thanks for the correction. So the original
comment is important and correct.
Powered by blists - more mailing lists