| commit | 9cc24e718a8501a86880a2c3b0cd6e7c12faf510 | [log] [tgz] |
|---|---|---|
| author | Anirudh Mathukumilli <rudymathu@fuchsia.infra.roller.google.com> | Wed Apr 16 15:58:25 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 16 16:00:43 2025 -0700 |
| tree | 231c36218cf79447ae0ccd4dd01e80f1ee1a085a | |
| parent | a562ba6f571a170a010b30b0e85de67552783785 [diff] |
[roll] Roll fuchsia [kernel] Ensure monotonicity of timelines during early-boot Dlog timestamps in early boot logs sometimes contained arbitrarily large values. This was caused by some kernel code that sampled the current boot time before the timer hardware had been initialized. See the attached bug for more details. This CL fixes the issue by ensuring that the timer register reads on ARM always return 0 until the timer hardware is initialized. The other architectures already return 0 during this interval, so no changes are required on x86 or RISC-V. Original-Fixed: 403329769 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1253654 Original-Revision: f50d675ac0db3aba77596a5ff398f713481f7029 GitOrigin-RevId: 7b2dfddcf7d584372a3c25fac5b63049f55a0abc Change-Id: I5eccdb9483eac5716f8d1d7028963e4782073723
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.