[Skiboot] [PATCH] chiptod: Keep boot timestamps contiguous
Stewart Smith
stewart at linux.vnet.ibm.com
Wed Dec 13 14:11:25 AEDT 2017
Oliver O'Halloran <oohall at gmail.com> writes:
> Currently we reset the timebase value to (almost) zero when
> synchronising the timebase of each chip to the Chip TOD network which
> results in this:
>
> [ 42.374813167,5] CPU: All 80 processors called in...
> [ 2.222791151,5] FLASH: Found system flash: Macronix MXxxL51235F id:0
> [ 2.222977933,5] BT: Interface initialized, IO 0x00e4
>
> This patch modifies the chiptod_init() process to use the current
> timebase value rather than resetting it to zero. This results in the
> timestamps remaining contigious from the start of hostboot until
> the petikernel starts. e.g.
>
> [ 70.188811484,5] CPU: All 144 processors called in...
> [ 72.458004252,5] FLASH: Found system flash: id:0
> [ 72.458147358,5] BT: Interface initialized, IO 0x00e4
>
> Signed-off-by: Oliver O'Halloran <oohall at gmail.com>
> ---
> Tested on a Witherspoon and a P8 FSP box. Seems to work ok in both
> cases.
> ---
> core/init.c | 8 +++++---
> hw/chiptod.c | 15 +++++++++++----
> 2 files changed, 16 insertions(+), 7 deletions(-)
Merged to master as of 5bb9d6f1e7dc0e38beb1db8f9f032a926310beac
Now I'm sure to be confused :)
--
Stewart Smith
OPAL Architect, IBM.
More information about the Skiboot
mailing list