[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z8uyzKfg0sfcfZB3@intel.com>
Date: Sat, 8 Mar 2025 11:00:28 +0800
From: Chao Gao <chao.gao@...el.com>
To: Dave Hansen <dave.hansen@...el.com>
CC: <tglx@...utronix.de>, <x86@...nel.org>, <seanjc@...gle.com>,
<pbonzini@...hat.com>, <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
<peterz@...radead.org>, <rick.p.edgecombe@...el.com>,
<weijiang.yang@...el.com>, <john.allen@....com>, <bp@...en8.de>, "Maxim
Levitsky" <mlevitsk@...hat.com>
Subject: Re: [PATCH v3 05/10] x86/fpu/xstate: Introduce guest FPU
configuration
On Fri, Mar 07, 2025 at 10:06:56AM -0800, Dave Hansen wrote:
>On 3/7/25 08:41, Chao Gao wrote:
>> + fpu_guest_cfg.max_features = fpu_kernel_cfg.max_features;
>> + fpu_guest_cfg.default_features = fpu_guest_cfg.max_features;
>> + fpu_guest_cfg.default_features &= ~XFEATURE_MASK_USER_DYNAMIC;
>
>Is just copying and pasting the 'fpu_kernel_cfg' initialization really
>the best way to explain what's going on?
>
>Let's say you just did:
>
> fpu_guest_cfg = fpu_kernel_cfg;
>
>?
>
>That would explicitly tell the reader that they're equal.
>
Yes. This is much better.
>
Powered by blists - more mailing lists