From: Dave Hansen <dave.hansen@intel.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"Gao, Chao" <chao.gao@intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "ebiggers@google.com" <ebiggers@google.com>,
"vigbalas@amd.com" <vigbalas@amd.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Bae, Chang Seok" <chang.seok.bae@intel.com>,
"levymitchell0@gmail.com" <levymitchell0@gmail.com>,
"samuel.holland@sifive.com" <samuel.holland@sifive.com>,
"Li, Xin3" <xin3.li@intel.com>,
"Yang, Weijiang" <weijiang.yang@intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
"john.allen@amd.com" <john.allen@amd.com>,
"Spassov, Stanislav" <stanspas@amazon.de>,
"attofari@amazon.de" <attofari@amazon.de>,
"Li, Rongqing" <lirongqing@baidu.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"aruna.ramakrishna@oracle.com" <aruna.ramakrishna@oracle.com>,
"bp@alien8.de" <bp@alien8.de>, "Liu, Zhao1" <zhao1.liu@intel.com>,
"ubizjak@gmail.com" <ubizjak@gmail.com>
Subject: Re: [PATCH v4 0/8] Introduce CET supervisor state support
Date: Wed, 2 Apr 2025 14:35:17 -0700 [thread overview]
Message-ID: <63abbc66-b237-4f7f-8aec-e32ebf6c62bd@intel.com> (raw)
In-Reply-To: <bd391db213179a52d68bb84531775117805d6932.camel@intel.com>
On 4/2/25 14:12, Edgecombe, Rick P wrote:
> In any case, at this point I think we need to either double down on polishing
> this thing up (by pausing other work) and have a clear “please do this with
> these patches" request, or declare failure and argue for the smaller version.
>
> I guess I still lean towards keeping the optimization. But I do think it's worth
> considering at this point.
I'm not quite feeling the same sense of panic and some need to pause
other work. This is thing is at v4. Between spring break and the merge
window, v4 hasn't gotten many eyeballs, except Chang's (thanks Chang!).
next prev parent reply other threads:[~2025-04-02 21:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 15:31 [PATCH v4 0/8] Introduce CET supervisor state support 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 ` [PATCH v4 0/8] Introduce CET supervisor state support Chang S. Bae
2025-04-02 21:12 ` Edgecombe, Rick P
2025-04-02 21:35 ` Dave Hansen [this message]
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=63abbc66-b237-4f7f-8aec-e32ebf6c62bd@intel.com \
--to=dave.hansen@intel.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=attofari@amazon.de \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=chao.gao@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