All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>, Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-efi@vger.kernel.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] efi: add ovmf debug log driver
Date: Wed, 9 Jul 2025 15:59:51 +0200	[thread overview]
Message-ID: <c2cec176-007b-4944-b72e-ce27290c98e0@kernel.org> (raw)
In-Reply-To: <CAMj1kXHd6__0Hcu1UyK+1obsK3bNsQh=1uBVWoaNsX1iTLx6CA@mail.gmail.com>

On 08/07/2025 15:06, Ard Biesheuvel wrote:
> On Tue, 8 Jul 2025 at 22:56, Gerd Hoffmann <kraxel@redhat.com> wrote:
>>
>> Recent OVMF versions (edk2-stable202508 + newer) can write their debug
>> log to a memory buffer.  This driver exposes the log content via sysfs
>> (/sys/firmware/efi/ovmf_debug_log).
>>
>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>> ---
>>  include/linux/efi.h                   |   2 +
>>  drivers/firmware/efi/efi.c            |   8 ++
>>  drivers/firmware/efi/ovmf-debug-log.c | 136 ++++++++++++++++++++++++++
>>  drivers/firmware/efi/Kconfig          |   8 ++
>>  drivers/firmware/efi/Makefile         |   1 +
>>  5 files changed, 155 insertions(+)
>>  create mode 100644 drivers/firmware/efi/ovmf-debug-log.c
>>
> 
> Thanks, I've queued this up now.

Giving people 10 minutes for review?

Best regards,
Krzysztof

  reply	other threads:[~2025-07-09 13:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 12:56 [PATCH v2] efi: add ovmf debug log driver Gerd Hoffmann
2025-07-08 13:06 ` Ard Biesheuvel
2025-07-09 13:59   ` Krzysztof Kozlowski [this message]
2025-07-09 13:58 ` Krzysztof Kozlowski
2025-07-09 14:17   ` Gerd Hoffmann
2025-07-09 14:20     ` Krzysztof Kozlowski
2025-07-09 14:31       ` Gerd Hoffmann
2025-07-09 14:39         ` Krzysztof Kozlowski
2025-07-09 14:40           ` Krzysztof Kozlowski
2025-07-09 23:14           ` Ard Biesheuvel
2025-07-10  6:41             ` Krzysztof Kozlowski

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=c2cec176-007b-4944-b72e-ce27290c98e0@kernel.org \
    --to=krzk@kernel.org \
    --cc=ardb@kernel.org \
    --cc=kraxel@redhat.com \
    --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 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.