mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	kexec@lists.infradead.org
Subject: Re: [PATCH] x86/setup: do not include kexec_handover.h from asm/setup.h
Date: Fri, 3 Jul 2026 08:11:11 -0700	[thread overview]
Message-ID: <20260703151111.GAakfRD6J8a1-g-aua@fat_crate.local> (raw)
In-Reply-To: <akdUX4vUEEJWrlGO@kernel.org>

On Fri, Jul 03, 2026 at 09:19:11AM +0300, Mike Rapoport wrote:
> The size does not matter ;-P

Yeah, that's what they all say :-P

> asm-generic would be my preference too if that's fine to include in
> decompressor.

Sure, the main idea is that if we add more linux/ namespace includes into the
decompressor, they end up pulling in the world and more and then you end up in
build and include hell. So we try to make sure only more or less
self-contained headers are included.

And there's a bunch of build magic in scripts/Makefile.asm-headers and this

# Support for using generic headers in asm-generic
asm-generic := -f $(srctree)/scripts/Makefile.asm-headers obj

in the main Makefile which lets you do things like that apparently:

$ git grep generic-y arch/x86/
arch/x86/include/asm/Kbuild:13:generic-y += early_ioremap.h
arch/x86/include/asm/Kbuild:14:generic-y += fprobe.h
arch/x86/include/asm/Kbuild:15:generic-y += mcs_spinlock.h
arch/x86/include/asm/Kbuild:16:generic-y += mmzone.h
arch/x86/include/asm/Kbuild:17:generic-y += ring_buffer.h

but you'd need to try it - I've only heard about it from the sidelines.

:-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2026-07-03 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 15:15 Pratyush Yadav
2026-07-01 16:57 ` Borislav Petkov
2026-07-02 19:31   ` Mike Rapoport
2026-07-03  0:11     ` Borislav Petkov
2026-07-03  6:19       ` Mike Rapoport
2026-07-03 15:11         ` Borislav Petkov [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=20260703151111.GAakfRD6J8a1-g-aua@fat_crate.local \
    --to=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@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