linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Wim Vervoorn <wvervoorn@eltan.com>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	Daniel Kiper <daniel.kiper@oracle.com>
Cc: coreboot@coreboot.org, LKML <linux-kernel@vger.kernel.org>,
	systemd-devel@lists.freedesktop.org,
	trenchboot-devel@googlegroups.com,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	x86@kernel.org, xen-devel@lists.xenproject.org, alecb@umass.edu,
	alexander.burmashev@oracle.com, allen.cryptic@gmail.com,
	andrew.cooper3@citrix.com, ard.biesheuvel@linaro.org,
	"btrotter@gmail.com" <btrotter@gmail.com>,
	dpsmith@apertussolutions.com, eric.devolder@oracle.com,
	eric.snowberg@oracle.com, hpa@zytor.com, hun@n-dimensional.de,
	javierm@redhat.com, joao.m.martins@oracle.com,
	kanth.ghatraju@oracle.com, konrad.wilk@oracle.com,
	krystian.hebel@3mdeb.com, leif@nuviainc.com,
	lukasz.hawrylko@intel.com, luto@amacapital.net,
	michal.zygowski@3mdeb.com, Matthew Garrett <mjg59@google.com>,
	mtottenh@akamai.com,
	Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
	piotr.krol@3mdeb.com, pjones@redhat.com, roger.pau@citrix.com,
	ross.philipson@oracle.com, tyhicks@linux.microsoft.com,
	Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [SPECIFICATION RFC] The firmware and bootloader log specification
Date: Tue, 8 Dec 2020 23:41:50 -0600	[thread overview]
Message-ID: <a173867b-49db-8147-de55-8d601f033036@gmail.com> (raw)
In-Reply-To: <9b614471-0395-88a5-1347-66417797e39d@molgen.mpg.de>

On 12/4/20 7:23 AM, Paul Menzel wrote:
> Dear Wim, dear Daniel,
> 
> 
> First, thank you for including all parties in the discussion.
> Am 04.12.20 um 13:52 schrieb Wim Vervoorn:
> 
>> I agree with you. Using an existing standard is better than inventing
>> a new one in this case. I think using the coreboot logging is a good
>> idea as there is indeed a lot of support already available and it is
>> lightweight and simple.
> In my opinion coreboot’s format is lacking, that it does not record the timestamp, and the log level is not stored as metadata, but (in coreboot) only used to decide if to print the message or not.
> 
> I agree with you, that an existing standard should be used, and in my opinion it’s Linux message format. That is most widely supported, and existing tools could then also work with pre-Linux messages.
> 
> Sean Hudson from Mentor Graphics presented that idea at Embedded Linux Conference Europe 2016 [1]. No idea, if anything came out of that effort. (Unfortunately, I couldn’t find an email. Does somebody have contacts at Mentor to find out, how to reach him?)

I forwarded this to Sean.

-Frank

> 
> 
> Kind regards,
> 
> Paul
> 
> 
> [1]: http://events17.linuxfoundation.org/sites/events/files/slides/2016-10-12%20-%20ELCE%20-%20Shared%20Logging%20-%20Part%20Deux.pdf


  parent reply	other threads:[~2020-12-09  5:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 23:52 [SPECIFICATION RFC] The firmware and bootloader log specification Daniel Kiper
2020-11-14  3:14 ` Randy Dunlap
2020-11-14 12:32 ` Nico Huber
2020-11-16  7:02 ` Antw: [EXT] [systemd-devel] " Ulrich Windl
2020-11-16  8:57   ` Rasmus Villemoes
2020-11-18 15:01 ` Heinrich Schuchardt
2020-12-03  1:17   ` Julius Werner
2020-12-04 12:52     ` Wim Vervoorn
2020-12-04 13:23       ` Paul Menzel
2020-12-07 21:50         ` Tom Rini
2020-12-09  5:41         ` Frank Rowand [this message]
2020-12-03 16:31 ` Andy Shevchenko
2020-12-15 20:25 ` Simon Glass

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=a173867b-49db-8147-de55-8d601f033036@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=alecb@umass.edu \
    --cc=alexander.burmashev@oracle.com \
    --cc=allen.cryptic@gmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=btrotter@gmail.com \
    --cc=coreboot@coreboot.org \
    --cc=daniel.kiper@oracle.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=eric.devolder@oracle.com \
    --cc=eric.snowberg@oracle.com \
    --cc=grub-devel@gnu.org \
    --cc=hpa@zytor.com \
    --cc=hun@n-dimensional.de \
    --cc=javierm@redhat.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kanth.ghatraju@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=krystian.hebel@3mdeb.com \
    --cc=leif@nuviainc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.hawrylko@intel.com \
    --cc=luto@amacapital.net \
    --cc=michal.zygowski@3mdeb.com \
    --cc=mjg59@google.com \
    --cc=mtottenh@akamai.com \
    --cc=phcoder@gmail.com \
    --cc=piotr.krol@3mdeb.com \
    --cc=pjones@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=roger.pau@citrix.com \
    --cc=ross.philipson@oracle.com \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=trenchboot-devel@googlegroups.com \
    --cc=tyhicks@linux.microsoft.com \
    --cc=u-boot@lists.denx.de \
    --cc=wvervoorn@eltan.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xypron.glpk@gmx.de \
    /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).