From: Borislav Petkov <bp@alien8.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/build: Do not allow X86_NATIVE_CPU to be enabled on non-x86_64 hosts
Date: Sun, 15 Nov 2026 07:52:42 -0800 [thread overview]
Message-ID: <20261115155242.GAavnVSv7VTBO51JGK@fat_crate.local> (raw)
In-Reply-To: <20261115050730.GB600738@ax162>
On Sat, Nov 14, 2026 at 10:07:30PM -0700, Nathan Chancellor wrote:
> Another option short of adding this test or killing it entirely would be
> depending on !COMPILE_TEST, as I only noticed this because
> CONFIG_X86_NATIVE_CPU gets enabled for allmodconfig.
This sounds better to me, TBH. As in: we don't need to do native CPU compile
tests in environments like cross-compiling on another uarch where this doesn't
even make sense to begin with.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-11-15 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 0:31 Nathan Chancellor
2026-11-14 20:25 ` Borislav Petkov
2026-11-14 20:46 ` Nathan Chancellor
2026-11-14 20:58 ` Borislav Petkov
2026-11-15 5:07 ` Nathan Chancellor
2026-11-15 15:52 ` Borislav Petkov [this message]
2026-11-16 18:28 ` Nick Desaulniers
2026-11-16 19:11 ` Nathan Chancellor
2026-11-16 22:28 ` David Laight
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=20261115155242.GAavnVSv7VTBO51JGK@fat_crate.local \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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®