Chrome OS is experimenting with a hypervisor layer that boots after firmware, but before the OS. From the OS' perspective, it can be considered an extension of firmware, and hence it makes sense to emit timestamp to track hypervisor boot latency. This change adds timestamp IDs in the 1200-1300 range for this purpose.
BUG=b:217638034 BRANCH=none TEST=Manual: cbmem -a TS_CRHV_BOOT to add a timestamp, cbmem -t to
verify that it got added to the timestamp table.
c8c6185d8e commonlib: Add timestamp IDs for Chrome OS hypervisor
.../include/commonlib/timestamp_serialized.h | 26 ++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)