From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Chao Gao <chao.gao@intel.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<tglx@linutronix.de>, <dave.hansen@intel.com>,
<seanjc@google.com>, <pbonzini@redhat.com>
Cc: <peterz@infradead.org>, <rick.p.edgecombe@intel.com>,
<weijiang.yang@intel.com>, <john.allen@amd.com>, <bp@alien8.de>,
<xin3.li@intel.com>, Adamos Ttofari <attofari@amazon.de>,
Aruna Ramakrishna <aruna.ramakrishna@oracle.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Eric Biggers <ebiggers@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
Li RongQing <lirongqing@baidu.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Mitchell Levy <levymitchell0@gmail.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
Stanislav Spassov <stanspas@amazon.de>,
Uros Bizjak <ubizjak@gmail.com>,
Vignesh Balasubramanian <vigbalas@amd.com>,
Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [PATCH v4 0/8] Introduce CET supervisor state support
Date: Tue, 1 Apr 2025 10:20:05 -0700 [thread overview]
Message-ID: <dc6617e5-2f97-431a-b3bf-6c87203a9301@intel.com> (raw)
In-Reply-To: <20250318153316.1970147-1-chao.gao@intel.com>
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
next prev parent reply other threads:[~2025-04-01 17:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 15:31 Chao Gao
2025-03-18 15:31 ` [PATCH v4 1/8] x86/fpu/xstate: Always preserve non-user xfeatures/flags in __state_perm Chao Gao
2025-04-01 17:17 ` Chang S. Bae
2025-04-01 17:56 ` Sean Christopherson
2025-03-18 15:31 ` [PATCH v4 2/8] x86/fpu: Drop @perm from guest pseudo FPU container Chao Gao
2025-04-01 17:16 ` Chang S. Bae
2025-04-02 1:56 ` Chao Gao
2025-03-18 15:31 ` [PATCH v4 3/8] x86/fpu/xstate: Add CET supervisor xfeature support Chao Gao
2025-04-01 17:15 ` Chang S. Bae
2025-04-02 2:28 ` Chao Gao
2025-04-02 21:37 ` Dave Hansen
2025-04-03 13:26 ` Chao Gao
2025-04-03 14:04 ` Ingo Molnar
2025-03-18 15:31 ` [PATCH v4 4/8] x86/fpu/xstate: Differentiate default features for host and guest FPUs Chao Gao
2025-04-01 17:18 ` Chang S. Bae
2025-04-02 3:16 ` Chao Gao
2025-03-18 15:31 ` [PATCH v4 5/8] x86/fpu: Initialize guest FPU permissions from guest defaults Chao Gao
2025-03-18 15:31 ` [PATCH v4 6/8] x86/fpu: Initialize guest fpstate and FPU pseudo container " Chao Gao
2025-03-18 15:31 ` [PATCH v4 7/8] x86/fpu/xstate: Introduce "guest-only" supervisor xfeature set Chao Gao
2025-04-01 17:16 ` Chang S. Bae
2025-04-02 4:29 ` Chao Gao
2025-03-18 15:31 ` [PATCH v4 8/8] x86/fpu/xstate: Warn if guest-only supervisor states are detected in normal fpstate Chao Gao
2025-04-01 17:17 ` Chang S. Bae
2025-04-02 14:30 ` Chao Gao
2025-04-04 0:02 ` Chang S. Bae
2025-04-04 1:06 ` Dave Hansen
2025-04-01 17:20 ` Chang S. Bae [this message]
2025-04-02 21:12 ` [PATCH v4 0/8] Introduce CET supervisor state support Edgecombe, Rick P
2025-04-02 21:35 ` Dave Hansen
2025-04-02 21:44 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc6617e5-2f97-431a-b3bf-6c87203a9301@intel.com \
--to=chang.seok.bae@intel.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=attofari@amazon.de \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=hpa@zytor.com \
--cc=john.allen@amd.com \
--cc=kvm@vger.kernel.org \
--cc=levymitchell0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=samuel.holland@sifive.com \
--cc=seanjc@google.com \
--cc=stanspas@amazon.de \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
--cc=vigbalas@amd.com \
--cc=weijiang.yang@intel.com \
--cc=x86@kernel.org \
--cc=xin3.li@intel.com \
--cc=zhao1.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®