[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aDjQ+dPeBsp7epmx@AUSJOHALLEN.amd.com>
Date: Thu, 29 May 2025 16:26:17 -0500
From: John Allen <john.allen@....com>
To: Chao Gao <chao.gao@...el.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
tglx@...utronix.de, dave.hansen@...el.com, seanjc@...gle.com,
pbonzini@...hat.com, peterz@...radead.org,
rick.p.edgecombe@...el.com, weijiang.yang@...el.com, bp@...en8.de,
chang.seok.bae@...el.com, xin3.li@...el.com,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Kees Cook <kees@...nel.org>,
Eric Biggers <ebiggers@...gle.com>,
Stanislav Spassov <stanspas@...zon.de>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH v8 4/6] x86/fpu: Remove xfd argument from
__fpstate_reset()
On Thu, May 22, 2025 at 08:10:07AM -0700, Chao Gao wrote:
> The initial values for fpstate::xfd differ between guest and host fpstates.
> Currently, the initial values are passed as an argument to
> __fpstate_reset(). But, __fpstate_reset() already assigns different default
> features and sizes based on the type of fpstates (i.e., guest or host). So,
> handle fpstate::xfd in a similar way to highlight the differences in the
> initial xfd value between guest and host fpstates
>
> Suggested-by: Sean Christopherson <seanjc@...gle.com>
> Signed-off-by: Chao Gao <chao.gao@...el.com>
Reviewed-by: John Allen <john.allen@....com>
Powered by blists - more mailing lists