From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-efi@vger.kernel.org
Subject: Re: [GIT PULL] EFI updates for v6.15
Date: Sun, 30 Mar 2025 10:10:23 +0200 [thread overview]
Message-ID: <Z-j8b7Z5oja05cCI@gmail.com> (raw)
In-Reply-To: <CAMj1kXF61PeyercrHdkevq+UdKvBsfJ4QV2RFJyXMWAYtJ95oQ@mail.gmail.com>
* Ard Biesheuvel <ardb@kernel.org> wrote:
> (cc Ingo)
>
> On Sat, 29 Mar 2025 at 19:46, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Fri, 28 Mar 2025 at 00:05, Ard Biesheuvel <ardb+git@google.com> wrote:
> > >
> > > arch/x86/boot/compressed/efi_mixed.S | 341 ---------------------
> > > drivers/firmware/efi/libstub/x86-mixed.S | 253 +++++++++++++++
> >
> > I've pulled this, but I'm not super-happy about it.
> >
> > We have been pretty successful in keeping assembler files in the
> > arch/ directory, and I really think we should strive to continue
> > that.
> >
> > Do we have a few drivers that have arch-specific assembly code?
> > Yes. But it certainly isn't something to make more common.
> >
> > And did we already do that zboot-header.S thing earlier? Also yes,
> > but that one is afaik actually architecture-neutral and doesn't
> > have any architecture *instructions* in it, it's just data layout
> > afaik (and no, I don't know why it was done as a '*.S' file)
> >
> > IOW, I really wish you would move this back to arch/x86 somewhere.
> > Please?
> >
>
> Fair enough. Note that this applies to la57toggle.S as well, which
> was moved in a patch that went via the -tip tree this cycle.
>
> It doesn't matter that much where the files live, as long as they are
> disentangled from the traditional decompressor. (For C files, it is
> important that they are built using the EFI stub's C flags, but for
> asm files, that makes little difference)
>
> Does arch/x86/lib sound like a reasonable place?
So all of this is boot code (early EFI runtime calls), right? Please
move anything fundamentally low level boot related to arch/x86/boot/.
We can open up arch/x86/boot/efi/ or so, to decouple it from the
decompressor.
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-30 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 7:05 [GIT PULL] EFI updates for v6.15 Ard Biesheuvel
2025-03-29 18:46 ` Linus Torvalds
2025-03-29 19:07 ` Ard Biesheuvel
2025-03-29 19:44 ` Linus Torvalds
2025-03-30 8:10 ` Ingo Molnar [this message]
2025-03-31 13:55 ` Ard Biesheuvel
2025-03-31 16:55 ` Ingo Molnar
2025-04-01 6:44 ` Ard Biesheuvel
2025-04-01 8:32 ` Ingo Molnar
2025-04-01 8:56 ` Ard Biesheuvel
2025-04-01 9:08 ` Ingo Molnar
2025-04-01 9:10 ` Ard Biesheuvel
2025-03-29 19:56 ` pr-tracker-bot
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=Z-j8b7Z5oja05cCI@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=torvalds@linux-foundation.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