From: Thomas Gleixner <tglx@linutronix.de>
To: Rob Landley <rob@landley.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: [PATCH 2/5] X86-64 should not uniquely require a third ELF package to build.
Date: Wed, 22 Feb 2023 00:12:26 +0100 [thread overview]
Message-ID: <87wn4amx45.ffs@tglx> (raw)
In-Reply-To: <e184ece9-2779-675e-0c84-f0a62413c7fd@landley.net>
Rob!
On Tue, Feb 21 2023 at 14:56, Rob Landley wrote:
The subject line is not compliant to documentation. Please read and
follow Documentation/process/* especially submitting-patches.rst and
maintainer-tip.rst
> x86-64 is the only architecture that can't compile without an extra
> ELF library installed on the host. (The kernel already has multiple ELF
> parse implementations built-in, so requiring another one is questionable
> at best.)
How are ELF parsers in the kernel itself related to a build requirement
for a tool, which is part of the kernel build process?
Next time you ask for removal of perl, python or whatever the kernel
requires to build.
> You can switch it back on in menuconfig if you want to, this
> just stops it being mandatory.
How do you switch on CONFIG_HAVE_OBJTOOL in menuconfig?
config HAVE_OBJTOOL
bool
There is no knob.
> See https://lkml.iu.edu/hypermail/linux/kernel/2110.3/00402.html
> and https://lkml.iu.edu/hypermail/linux/kernel/2110.3/00278.html
Please use https://lore.kernel.org/lkml/ links.
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 3604074a878b..b63510d79baf 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -243,7 +243,6 @@ config X86
> select HAVE_NOINSTR_HACK if HAVE_OBJTOOL
> select HAVE_NMI
> select HAVE_NOINSTR_VALIDATION if HAVE_OBJTOOL
> - select HAVE_OBJTOOL if X86_64
This prevents runtime features, optimizations, mitigations and build
time validations rom being selected as you can see from your patch
context.
Just to be clear: objtool is mandatory for x86_64 builds.
git grep 'select HAVE_OBJTOOL' will tell you that your claim about
x86_64 being the only architecture is slightly wrong.
Thanks,
tglx
next prev parent reply other threads:[~2023-02-21 23:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:53 [PATCH 0/5] Patches used to build mkroot Rob Landley
2023-02-21 20:55 ` [PATCH 1/5] try generic compiler name "cc" before falling back to "gcc" Rob Landley
2023-02-23 5:31 ` Masahiro Yamada
2023-02-23 13:50 ` Rob Landley
2023-02-24 0:27 ` Masahiro Yamada
2023-02-21 20:56 ` [PATCH 2/5] X86-64 should not uniquely require a third ELF package to build Rob Landley
2023-02-21 23:12 ` Thomas Gleixner [this message]
2023-02-22 18:14 ` Rob Landley
2023-02-22 18:41 ` Thomas Gleixner
2023-02-21 20:57 ` [PATCH 3/5] Wire up CONFIG_DEVTMPFS_MOUNT to initramfs Rob Landley
2023-02-21 21:00 ` [PATCH 4/5] Replace timeconst.bc with mktimeconst.c Rob Landley
2023-02-21 23:53 ` Thomas Gleixner
2023-02-22 22:52 ` Rob Landley
2023-02-21 21:04 ` [PATCH 5/5] fix rootfstype=tmpfs Rob Landley
2023-11-01 13:10 ` Stefan Berger
2023-11-08 22:05 ` Stefan Berger
2023-11-09 16:42 ` Rob Landley
2023-11-09 16:46 ` Rob Landley
2023-11-09 16:55 ` Rob Landley
2023-02-23 20:35 ` [PATCH 0/5] Patches used to build mkroot Andrew Morton
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=87wn4amx45.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rob@landley.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.