From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>,
coreboot@coreboot.org, grub-devel@gnu.org,
trenchboot-devel@googlegroups.com, x86@kernel.org,
u-boot@lists.denx.de,
"systemd-devel@lists.freedesktop.org"
<systemd-devel@lists.freedesktop.org>,
xen-devel@lists.xenproject.org, daniel.kiper@oracle.com,
linux-kernel@vger.kernel.org
Cc: krystian.hebel@3mdeb.com, michal.zygowski@3mdeb.com,
piotr.krol@3mdeb.com, mtottenh@akamai.com, luto@amacapital.net,
dpsmith@apertussolutions.com, andrew.cooper3@citrix.com,
roger.pau@citrix.com, allen.cryptic@gmail.com,
btrotter@gmail.com, phcoder@gmail.com, lukasz.hawrylko@intel.com,
ard.biesheuvel@linaro.org, tyhicks@linux.microsoft.com,
pmenzel@molgen.mpg.de, hun@n-dimensional.de, leif@nuviainc.com,
alexander.burmashev@oracle.com, eric.devolder@oracle.com,
eric.snowberg@oracle.com, joao.m.martins@oracle.com,
kanth.ghatraju@oracle.com, konrad.wilk@oracle.com,
ross.philipson@oracle.com, javierm@redhat.com, pjones@redhat.com,
alecb@umass.edu, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Antw: [EXT] [systemd-devel] [SPECIFICATION RFC] The firmware and bootloader log specification
Date: Mon, 16 Nov 2020 09:57:25 +0100 [thread overview]
Message-ID: <2d920ff2-68cb-69f5-f2d9-47131ec1b512@prevas.dk> (raw)
In-Reply-To: <5FB223E8020000A10003CB88@gwsmtp.uni-regensburg.de>
On 16/11/2020 08.02, Ulrich Windl wrote:
>>>> Daniel Kiper <daniel.kiper@oracle.com> schrieb am 14.11.2020 um 00:52 in
> Nachricht <20201113235242.k6fzlwmwm2xqhqsi@tomti.i.net-space.pl>:
> ...
>> The members of struct bf_log_msg:
>> ‑ size: total size of bf_log_msg struct,
>> ‑ ts_nsec: timestamp expressed in nanoseconds starting from 0,
>
> Who or what defines t == 0?
Some sort of "clapperboard" log entry, stating "the RTC says X, the
cycle counter is Y, the onboard ACME atomic clock says Z, I'm now
starting to count ts_nsec from W" might be useful for some eventual
userspace tool to try to stitch together the log entries from the
various stages. I have no idea how a formal spec of such an entry would
look like or if it's even feasible to do formally. But even just such
entries in free-form prose could at least help a human consumer.
Rasmus
next prev parent reply other threads:[~2020-11-16 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 23:52 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 [this message]
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
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=2d920ff2-68cb-69f5-f2d9-47131ec1b512@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®