[roll] Roll fuchsia [kernel][lockup] Refactor mp_all_cpu_startup_sync_hook

Refactor mp_all_cpu_startup_sync_hook to use the new
CanDumpRegistersAndBacktrace function and expand on rationale for why
it's OK to panic there on production builds.

On production builds, if one or more secondaries fail to start up,
we'll attempt to dump diagnostics from the CPUs that failed to
check-in and then panic.  On development builds, we'll emit an oops
instead.  See the comments in the code for the rationale.

Change x86's DumpRegistersAndBacktrace implementation to not require
that interrupts are disabled.  This fixes a potential bug where we
might otherwise recursively panic.

Manually tested by hacking up the secondary startup to force them to
fail to check in, then verifying that we oops or panic.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1194248
Original-Revision: 57951b353b3569540217b1e6efad83c6aa6545b0
GitOrigin-RevId: 9a1f0d4383e2f182624c1b073888351b04dda85e
Change-Id: I452afdbf5c58ceda477135bf546d335cc9d55903
1 file changed
tree: 7802a40797ceb0108bf254a2e5e95d1d84f7c6dd
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.