From: Xi Ruoyao <xry111@xry111.site>
To: Mingcong Bai <jeffbai@aosc.io>, linux-kernel@vger.kernel.org
Cc: "Kexy Biscuit" <kexybiscuit@aosc.io>,
"Thomas Gleixner" <tglx@kernel.org>,
"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>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Nick Terrell" <terrelln@fb.com>,
"David Sterba" <dsterba@suse.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Jan Stancek" <jstancek@redhat.com>,
"Josh Poimboeuf" <jpoimboe@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Simon Glass" <sjg@chromium.org>,
"Marco Elver" <elver@google.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH] x86/boot: use zstd -19 if building for 32-bit
Date: Tue, 28 Jul 2026 22:42:48 +0800 [thread overview]
Message-ID: <262a4063b76b96dcb76a226bb44fd65cb2297d94.camel@xry111.site> (raw)
In-Reply-To: <20260728143141.2870515-1-jeffbai@aosc.io>
On Tue, 2026-07-28 at 22:31 +0800, Mingcong Bai wrote:
> When using native build environments (that is, 32-bit x86 chroot/container
> as build environment for 32-bit x86 binaries), `zstd -22' requests more
> virtual memory than that could be allowed on 32-bit hosts.
>
> Introduce `cmd_zstd_with_size' for CONFIG_X86_32 builds.
>
> This is quite possibly just stupid... But there doesn't seem to be a way
> to detect the host environment. So I'm sending this patch as a means to
> ask for your opinions.
"readelf -d $(which zstd) -h | grep ELF64" ?
But it's also stupid, if someone is using a script wrapping the actual
zstd executable or cross-compiling from a non-ELF platform things will
still blow up.
--
Xi Ruoyao <xry111@xry111.site>
next prev parent reply other threads:[~2026-07-28 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 14:31 Mingcong Bai
2026-07-28 14:42 ` Xi Ruoyao [this message]
2026-07-28 15:58 ` Ard Biesheuvel
2026-07-29 1:44 ` Mingcong Bai
2026-07-28 16:05 ` H. Peter Anvin
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=262a4063b76b96dcb76a226bb44fd65cb2297d94.camel@xry111.site \
--to=xry111@xry111.site \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dsterba@suse.com \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=jeffbai@aosc.io \
--cc=jpoimboe@kernel.org \
--cc=jstancek@redhat.com \
--cc=kexybiscuit@aosc.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sjg@chromium.org \
--cc=terrelln@fb.com \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--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®