From: Daniel Kiper <daniel.kiper@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: grub-devel@gnu.org, linux-kernel@vger.kernel.org,
trenchboot-devel@googlegroups.com, x86@kernel.org,
xen-devel@lists.xenproject.org, alec.brown@oracle.com,
alexander.burmashev@oracle.com, andrew.cooper3@citrix.com,
ard.biesheuvel@linaro.org, dpsmith@apertussolutions.com,
eric.snowberg@oracle.com, hpa@zytor.com, javierm@redhat.com,
kanth.ghatraju@oracle.com, konrad.wilk@oracle.com,
krystian.hebel@3mdeb.com, leif@nuviainc.com,
lukasz.hawrylko@linux.intel.com, michal.zygowski@3mdeb.com,
mjg59@google.com, mtottenh@akamai.com, phcoder@gmail.com,
piotr.krol@3mdeb.com, pjones@redhat.com,
ross.philipson@oracle.com
Subject: Re: [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others
Date: Mon, 1 Jun 2020 11:56:05 +0200 [thread overview]
Message-ID: <20200601095605.oxhq74llusb7k6ma@tomti.i.net-space.pl> (raw)
In-Reply-To: <7FE0DF48-C221-460E-99D5-00E42128283C@amacapital.net>
On Fri, May 29, 2020 at 10:11:40AM -0700, Andy Lutomirski wrote:
> > On May 29, 2020, at 4:30 AM, Daniel Kiper <daniel.kiper@oracle.com> wrote:
> >
> > Hey,
> >
> > Below you can find my rough idea of the bootloader log format which is
> > generic thing but initially will be used for TrenchBoot work. I discussed
> > this proposal with Ross and Daniel S. So, the idea went through initial
> > sanitization. Now I would like to take feedback from other folks too.
> > So, please take a look and complain...
>
> > In general we want to pass the messages produced by the bootloader to the OS
> > kernel and finally to the userspace for further processing and analysis. Below
> > is the description of the structures which will be used for this thing.
>
> Is the intent for a human to read these, or to get them into the
> system log file, or are they intended to actually change the behavior
> of the system?
>
> IOW, what is this for?
In general the idea is for a human to read these. There will be a separate
tool which reads the bootloader log exposed via Linux kernel sysfs and displays
its contents to the user. The tool will allow user to do various kinds of
filtering. We are not going to put the contents of the bootloader log into any
of system logs. However, if somebody wants to do that, in sensible way, I am
OK with that.
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Kiper <daniel.kiper@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: dpsmith@apertussolutions.com, alexander.burmashev@oracle.com,
krystian.hebel@3mdeb.com, hpa@zytor.com,
michal.zygowski@3mdeb.com, grub-devel@gnu.org, x86@kernel.org,
javierm@redhat.com, kanth.ghatraju@oracle.com,
ross.philipson@oracle.com, xen-devel@lists.xenproject.org,
leif@nuviainc.com, trenchboot-devel@googlegroups.com,
alec.brown@oracle.com, mtottenh@akamai.com,
konrad.wilk@oracle.com, phcoder@gmail.com, piotr.krol@3mdeb.com,
ard.biesheuvel@linaro.org, andrew.cooper3@citrix.com,
linux-kernel@vger.kernel.org, mjg59@google.com,
eric.snowberg@oracle.com, pjones@redhat.com,
lukasz.hawrylko@linux.intel.com
Subject: Re: [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others
Date: Mon, 1 Jun 2020 11:56:05 +0200 [thread overview]
Message-ID: <20200601095605.oxhq74llusb7k6ma@tomti.i.net-space.pl> (raw)
In-Reply-To: <7FE0DF48-C221-460E-99D5-00E42128283C@amacapital.net>
On Fri, May 29, 2020 at 10:11:40AM -0700, Andy Lutomirski wrote:
> > On May 29, 2020, at 4:30 AM, Daniel Kiper <daniel.kiper@oracle.com> wrote:
> >
> > Hey,
> >
> > Below you can find my rough idea of the bootloader log format which is
> > generic thing but initially will be used for TrenchBoot work. I discussed
> > this proposal with Ross and Daniel S. So, the idea went through initial
> > sanitization. Now I would like to take feedback from other folks too.
> > So, please take a look and complain...
>
> > In general we want to pass the messages produced by the bootloader to the OS
> > kernel and finally to the userspace for further processing and analysis. Below
> > is the description of the structures which will be used for this thing.
>
> Is the intent for a human to read these, or to get them into the
> system log file, or are they intended to actually change the behavior
> of the system?
>
> IOW, what is this for?
In general the idea is for a human to read these. There will be a separate
tool which reads the bootloader log exposed via Linux kernel sysfs and displays
its contents to the user. The tool will allow user to do various kinds of
filtering. We are not going to put the contents of the bootloader log into any
of system logs. However, if somebody wants to do that, in sensible way, I am
OK with that.
Daniel
next prev parent reply other threads:[~2020-06-01 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 11:27 [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others Daniel Kiper
2020-05-29 11:27 ` Daniel Kiper
2020-05-29 17:11 ` Andy Lutomirski
2020-05-29 17:11 ` Andy Lutomirski
2020-06-01 9:56 ` Daniel Kiper [this message]
2020-06-01 9:56 ` Daniel Kiper
2020-06-01 10:54 ` Roger Pau Monné
2020-06-01 10:54 ` Roger Pau Monné
2020-06-01 18:25 ` Hans Ulrich Niedermann
2020-06-01 18:25 ` Hans Ulrich Niedermann
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=20200601095605.oxhq74llusb7k6ma@tomti.i.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=alec.brown@oracle.com \
--cc=alexander.burmashev@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dpsmith@apertussolutions.com \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=hpa@zytor.com \
--cc=javierm@redhat.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@linux.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=ross.philipson@oracle.com \
--cc=trenchboot-devel@googlegroups.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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.