mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
	<tglx@kernel.org>, <mingo@redhat.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <hpa@zytor.com>,
	Omar Avelar <omar.avelar@intel.com>, <stable@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>,
	"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH] x86/build/64: Prevent native builds from generating APX instructions
Date: Thu, 27 Aug 2026 08:40:19 -0700	[thread overview]
Message-ID: <dca20e1a-1f14-47cf-b154-1979e9248bea@intel.com> (raw)
In-Reply-To: <20260712202538.GA1697833@ax162>

On 7/12/2026 1:25 PM, Nathan Chancellor wrote:
> 
> Miguel's comment aside:
> 
> Reviewed-by: Nathan Chancellor <nathan@kernel.org>

Thanks!

> As the flag is the same between the two compilers, I think it would be
> more readable to do something like:
> 
>    # Do not generate APX instructions as in-kernel use isn't ready
>    # Supported by GCC 14+ and LLVM 18+
>    KBUILD_CFLAGS += $(call cc-option,-mno-apxf)
Yeah, thanks -- I took this for V2.

BTW now I realized that both compilers already support `apx-features=` 
to specify sub-options. Instead of -mno-apxf entirely, 
-mno-apx-features="egpr" can just disable the use of EGPRs.

Thanks,
Chang

  reply	other threads:[~2026-08-27 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 21:14 Chang S. Bae
2026-07-09 12:36 ` Miguel Ojeda
2026-07-14 22:15   ` Chang S. Bae
2026-07-15 10:30     ` Miguel Ojeda
2026-07-31 20:46       ` Chang S. Bae
2026-07-31 20:57         ` Miguel Ojeda
2026-07-31 21:15           ` Chang S. Bae
2026-07-12 20:25 ` Nathan Chancellor
2026-08-27 15:40   ` Chang S. Bae [this message]
2026-08-01 11:44 ` David Laight
2026-08-02  0:00   ` Chang S. Bae
2026-08-02  9:08     ` David Laight
2026-08-02 21:32       ` Chang S. Bae

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=dca20e1a-1f14-47cf-b154-1979e9248bea@intel.com \
    --to=chang.seok.bae@intel.com \
    --cc=arjan.van.de.ven@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=omar.avelar@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@kernel.org \
    --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®