[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc6617e5-2f97-431a-b3bf-6c87203a9301@intel.com>
Date: Tue, 1 Apr 2025 10:20:05 -0700
From: "Chang S. Bae" <chang.seok.bae@...el.com>
To: Chao Gao <chao.gao@...el.com>, <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>
CC: <peterz@...radead.org>, <rick.p.edgecombe@...el.com>,
<weijiang.yang@...el.com>, <john.allen@....com>, <bp@...en8.de>,
<xin3.li@...el.com>, Adamos Ttofari <attofari@...zon.de>, Aruna Ramakrishna
<aruna.ramakrishna@...cle.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
Eric Biggers <ebiggers@...gle.com>, "H. Peter Anvin" <hpa@...or.com>, "Ingo
Molnar" <mingo@...hat.com>, Li RongQing <lirongqing@...du.com>, Maxim
Levitsky <mlevitsk@...hat.com>, Mitchell Levy <levymitchell0@...il.com>,
"Samuel Holland" <samuel.holland@...ive.com>, Stanislav Spassov
<stanspas@...zon.de>, Uros Bizjak <ubizjak@...il.com>, Vignesh
Balasubramanian <vigbalas@....com>, Zhao Liu <zhao1.liu@...el.com>
Subject: Re: [PATCH v4 0/8] Introduce CET supervisor state support
On 3/18/2025 8:31 AM, Chao Gao wrote:
>
> arch/x86/include/asm/fpu/types.h | 58 ++++++++++++++++++++++---------
> arch/x86/include/asm/fpu/xstate.h | 9 +++--
> arch/x86/kernel/fpu/core.c | 36 ++++++++++++-------
> arch/x86/kernel/fpu/xstate.c | 42 +++++++++++++++-------
> arch/x86/kernel/fpu/xstate.h | 2 ++
> 5 files changed, 102 insertions(+), 45 deletions(-)
Hi Chao Gao,
I've left a few comments on your patches. It looks like the structure of
your patch set has been shifting between postings. I’d recommend
reviewing the build-up of changes more carefully — see my reply on patch3.
Additionally, your approach to the ongoing discussion comes across as
somewhat reserved. Since you’re presenting a counterpoint to the
maintainer’s suggestion, I’d encourage you to articulate your reasoning
more clearly (see my comment on patch 7).
Most of other feedback focuses on refining individual changes.
Specifically, your upcoming modifications to the initialization sequence
do not look super clear. My suggestions in patch 4 reflect my
interpretation, but please consider whether there's a clearer way to
present the new configuration settings.
Thanks,
Chang
Powered by blists - more mailing lists