From: Hendrik 'T4cC0re' Meyer <linux@t4c.dev>
To: ardb@kernel.org
Cc: linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@t4c.dev
Subject: [PATCH] efistub: add efi=quiet parameter to selectively silence efistub alone
Date: Sun, 19 Jan 2025 18:32:05 +0100 [thread overview]
Message-ID: <20250119173205.2965649-1-linux@t4c.dev> (raw)
In-Reply-To: <CAMj1kXGLGmKU1Nvz8oo-aui1AtWo_8YDdT9cGtVweV9d6K6D3A@mail.gmail.com>
Hello!
> Could you explain the use case please? Your concern is that removing
'quiet' from the command line is producing a few additional lines of
output from the EFI stub at boot?
Sure :) I boot a UKI (with Secure Boot and TPM measurements) with an
embedded splash image, and the cmdline
'memtest=2 earlyprintk=serial,ttyS0,115200 console=ttyS0,115200n8'
The stub by default (without 'quiet') will print messages regarding
the UKI and it being measured into the TPM on the efifb (I assume)
rendering on top of the displayed splash image.
"EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path"
and "EFI stub: Measured initrd data into PCR 9" to be specific.
> How is that a problem compared to
the fact that you get the entire kernel log printed to the console?
Very relevant question. Because of the 'memtest=2' flag, there is a
delay during boot, which should be logged (with memtest progress) to
the serial console. 'quiet' will silence these logs.
> Is every single line printed there relevant to you, and only the ones
emitted by the EFI stub are not?
Basically, yes. I want the kernel's printk's, but not have the output
of the efistub dipsplayed on top of the splash screen of the UKI.
I did not find a way to redirect this output, and adding a 'efi=quiet'
option seemed like a low hanging fruit.
Hendrik
next prev parent reply other threads:[~2025-01-19 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 2:44 [PATCH] efistub: add efi=quiet parameter to selectively silence efistub alone Hendrik 'T4cC0re' Meyer
2025-01-19 17:11 ` Ard Biesheuvel
2025-01-19 17:32 ` Hendrik 'T4cC0re' Meyer [this message]
2025-01-20 8:45 ` Ard Biesheuvel
2025-01-20 8:52 ` Hendrik 'T4cC0re' Meyer
2025-01-20 8:54 ` Ard Biesheuvel
2025-01-20 9:13 ` Hendrik 'T4cC0re' Meyer
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=20250119173205.2965649-1-linux@t4c.dev \
--to=linux@t4c.dev \
--cc=ardb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).