[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <742a95cece1998673aa360be10036c82c0c535ec.camel@intel.com>
Date: Tue, 28 Nov 2023 14:58:26 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "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>,
"Hansen, Dave" <dave.hansen@...el.com>
CC: "john.allen@....com" <john.allen@....com>,
"peterz@...radead.org" <peterz@...radead.org>,
"Gao, Chao" <chao.gao@...el.com>,
"mlevitsk@...hat.com" <mlevitsk@...hat.com>
Subject: Re: [PATCH v7 05/26] x86/fpu/xstate: Introduce fpu_guest_cfg for
guest FPU configuration
On Fri, 2023-11-24 at 00:53 -0500, Yang Weijiang wrote:
> + /*
> + * Set guest's __user_state_size to fpu_user_cfg.default_size
> so that
> + * existing uAPIs can still work.
> + */
> + fpu->guest_perm.__user_state_size =
> fpu_user_cfg.default_size;
It seems like an appropriate value, but where does this come into play
exactly for guest FPUs?
Powered by blists - more mailing lists