[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Antw: [EXT] [systemd-devel] [SPECIFICATION RFC] The firmware and bootloader log specification
- To: Ulrich Windl <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>, coreboot@xxxxxxxxxxxx, grub-devel@xxxxxxx, trenchboot-devel@xxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, u-boot@xxxxxxxxxxxxx, "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, daniel.kiper@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- From: Rasmus Villemoes <rasmus.villemoes@xxxxxxxxx>
- Date: Mon, 16 Nov 2020 09:57:25 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=prevas.dk; dmarc=pass action=none header.from=prevas.dk; dkim=pass header.d=prevas.dk; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gb1mYEH6RieZNFdbTWVSUF50n4VJM1Gg9ilylfzVafw=; b=Ys/deUSSXRPGrW0PSQInno+CRz45Z/8tsERQI2Br5727Zo9daJ9j+NFIRhJu0qcw5CHEthrf+g4MabMInyVaKvewmaOiPw+wbthM+rKT1xRhHfuBC/iKBBWqazUlDoqo0jkG0plEachOQderdiLqx6MHSl3RnrrUgK10qNUCcjnT2jA2UKqjtDUdpAOz1tt3C0NoJg78X8ACTRnHQ0VFMu0jh+SaJKUsz9y/WR4gyApg80QW+xsY6ALYLPJT5t5y8hdMRgrmGW6s0MlB7RhVjsyt+IKVAeYAYlZSS/Ubq2b6H36fyymFhRPZivjNOAI9T/cDqmre+MxhFSY1QRQNZg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XqFMujluC4+O+8vVvlUhTo+FuwcO67sZhl7HXvCaH9cWRWtKT0gK0d2KHBLEfuJ6sRRr0OONtzMq/5QR39cQ6PxHQhCzG7qzIoJWVnv8JJgXjAUV3XyGfKMym2+UwzQewPq9rlhOmWbTXkE7w+Vh4FpZvZx5mHPs5jNF0WPwqyCQN//duDSyCweQvS5ocQapLfrAXSPjpWhFFbmA43sE0MNVDrpPdmomVXFSYadf0WKhFxVJiCVJVsUJD8gDRfu42dLZfALruodp4j+SFff4yDB/ufKnvFr7vpXPG4l6ka0+mfVeLQ2so9D4gv3Nri7/1016JcUVo/aX6l2E/qP9/A==
- Authentication-results: zytor.com; dkim=none (message not signed) header.d=none;zytor.com; dmarc=none action=none header.from=prevas.dk;
- Cc: krystian.hebel@xxxxxxxxx, michal.zygowski@xxxxxxxxx, piotr.krol@xxxxxxxxx, mtottenh@xxxxxxxxxx, luto@xxxxxxxxxxxxxx, dpsmith@xxxxxxxxxxxxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, roger.pau@xxxxxxxxxx, allen.cryptic@xxxxxxxxx, btrotter@xxxxxxxxx, phcoder@xxxxxxxxx, lukasz.hawrylko@xxxxxxxxx, ard.biesheuvel@xxxxxxxxxx, tyhicks@xxxxxxxxxxxxxxxxxxx, pmenzel@xxxxxxxxxxxxx, hun@xxxxxxxxxxxxxxxx, leif@xxxxxxxxxxxx, alexander.burmashev@xxxxxxxxxx, eric.devolder@xxxxxxxxxx, eric.snowberg@xxxxxxxxxx, joao.m.martins@xxxxxxxxxx, kanth.ghatraju@xxxxxxxxxx, konrad.wilk@xxxxxxxxxx, ross.philipson@xxxxxxxxxx, javierm@xxxxxxxxxx, pjones@xxxxxxxxxx, alecb@xxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>
- Delivery-date: Mon, 16 Nov 2020 09:49:42 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 16/11/2020 08.02, Ulrich Windl wrote:
>>>> Daniel Kiper <daniel.kiper@xxxxxxxxxx> schrieb am 14.11.2020 um 00:52 in
> Nachricht <20201113235242.k6fzlwmwm2xqhqsi@xxxxxxxxxxxxxxxxxxxx>:
> ...
>> 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
|
