[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276CA6A8D1CF84F196C40598C759@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Tue, 14 Dec 2021 07:16:06 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Paolo Bonzini <pbonzini@...hat.com>,
"Zhong, Yang" <yang.zhong@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Subject: RE: [PATCH 10/19] kvm: x86: Emulate WRMSR of guest IA32_XFD
Hi, Thomas,
> From: Thomas Gleixner <tglx@...utronix.de>
> Sent: Tuesday, December 14, 2021 5:23 AM
>
> Paolo,
>
> On Mon, Dec 13 2021 at 20:45, Thomas Gleixner wrote:
> > On Mon, Dec 13 2021 at 16:06, Paolo Bonzini wrote:
> >> That said, I think xfd_update_state should not have an argument.
> >> current->thread.fpu.fpstate->xfd is the only fpstate that should be
> >> synced with the xfd_state per-CPU variable.
> >
> > I'm looking into this right now. The whole restore versus runtime thing
> > needs to be handled differently.
>
After looking at your series, I think it missed Paolo's comment
about changing xfd_update_state() to accept no argument.
Thanks
Kevin
Powered by blists - more mailing lists