From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<rust-for-linux@vger.kernel.org>, <tglx@kernel.org>,
<mingo@redhat.com>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>, <ojeda@kernel.org>, <nathan@kernel.org>,
<boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <aliceryhl@google.com>,
<tmgross@umich.edu>, <dakr@kernel.org>,
<daniel.almeida@collabora.com>, <tamird@kernel.org>,
<acourbot@nvidia.com>, <work@onurozkan.dev>,
Omar Avelar <omar.avelar@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2] x86/build/64: Prevent native builds from generating APX instructions
Date: Thu, 3 Sep 2026 07:10:58 -0700 [thread overview]
Message-ID: <0b7180af-9cd7-4a01-af91-c2b4acac624a@intel.com> (raw)
In-Reply-To: <20260903052325.GKapkETZDh2AU8aWNP@fat_crate.local>
On 9/2/2026 10:23 PM, Borislav Petkov wrote:
>
> I can take a v2 with feedback from this thread integrated.
>
Thanks for the consideration! But there is one more thing to do:
Recently we found a sub-option in both compilers to disable EGPR use
only while allowing other APX features. Let me conclude this in V3.
Sorry, I should have commented this here.
Thanks,
Chang
prev parent reply other threads:[~2026-09-03 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 15:17 Chang S. Bae
2026-08-07 16:58 ` Miguel Ojeda
2026-08-08 3:21 ` Chang S. Bae
2026-08-10 15:24 ` Miguel Ojeda
2026-09-03 5:23 ` Borislav Petkov
2026-09-03 14:10 ` Chang S. Bae [this message]
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=0b7180af-9cd7-4a01-af91-c2b4acac624a@intel.com \
--to=chang.seok.bae@intel.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=bp@alien8.de \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dave.hansen@linux.intel.com \
--cc=gary@garyguo.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=omar.avelar@intel.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=x86@kernel.org \
/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®