All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] efi: add ovmf debug log driver
Date: Wed, 9 Jul 2025 16:20:49 +0200	[thread overview]
Message-ID: <8621135e-445a-42dd-89e0-bf8fc3e2b6b7@kernel.org> (raw)
In-Reply-To: <2mn65slwkwmjpeilma2isw7zgabdmda4rhpqjiutwdwqno2wrh@zghymlce2fiy>

On 09/07/2025 16:17, Gerd Hoffmann wrote:
> On Wed, Jul 09, 2025 at 03:58:58PM +0200, Krzysztof Kozlowski wrote:
>> On 08/07/2025 14:56, Gerd Hoffmann wrote:
>>> +MODULE_DESCRIPTION("OVMF debug log");
>>> +MODULE_AUTHOR("Gerd Hoffmann <kraxel@redhat.com>");
>>> +MODULE_LICENSE("GPL");
>>> +MODULE_ALIAS("platform:ovmf_debug_log");
>>> diff --git a/drivers/firmware/efi/Kconfig b/drivers/firmware/efi/Kconfig
>>> index db8c5c03d3a2..ac0a03ec3452 100644
>>> --- a/drivers/firmware/efi/Kconfig
>>> +++ b/drivers/firmware/efi/Kconfig
>>> @@ -263,6 +263,14 @@ config EFI_COCO_SECRET
>>>  	  virt/coco/efi_secret module to access the secrets, which in turn
>>>  	  allows userspace programs to access the injected secrets.
>>>  
>>> +config OVMF_DEBUG_LOG
>>> +	tristate "Expose OVMF firmware debug log via sysfs"
>>> +	depends on EFI
>>> +	help
>>> +	  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).
>>
>> Where did you document new ABI?
> 
> The log buffer header struct is documented in the header file for the
> edk2 code:
> https://github.com/tianocore/edk2/blob/master/OvmfPkg/Include/Library/MemDebugLogLib.h

You added a new sysfs interface. I meant documentation for this.

Best regards,
Krzysztof

  reply	other threads:[~2025-07-09 14:20 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
2025-07-09 13:58 ` Krzysztof Kozlowski
2025-07-09 14:17   ` Gerd Hoffmann
2025-07-09 14:20     ` Krzysztof Kozlowski [this message]
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=8621135e-445a-42dd-89e0-bf8fc3e2b6b7@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.