[roll] Roll fuchsia [mexec] Fit mexec into orderly shutdown

mexec path before:
* netsvc calls into the deprecated fuchsia.device.manager.Administrator
service to suspend all drivers
* netsvc calls zx_system_mexec()

mexec path after:
* netsvc calls into fuchsia.hardware.power.statecontrol.Admin - backed
by the shutdown-shim to take control of performing the mexec
* the shutdown-shim configures driver_manager to perform the actual
mexec on shutdown, after it has suspended all drivers
* the shutdown-shim initiates an orderly system shutdown to indirectly
trigger the mexec.

Why?
* Shutting down is the purview of the shutdown-shim;
* We remove the knob to isolatedly attempt to shutdown the
driver_manager outside of the context of the component framework's
lifecycle management;
* We localize the knowledge of when it is safe to mexec with the only
thing that truly knows.

Original-Fixed: 57448
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/586324
Original-Revision: 8422ff294110f8b88024849ab81f836290bc6aec
GitOrigin-RevId: bca545e49771fe769808f842552cf0e03ec72771
Change-Id: I2dacc934b606f2dad0a6a26b0edf9a36e034b1fc
1 file changed
tree: e81e2028fa1f599f3db9c41f38822689a1fb2f2b
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. test_durations
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 via the IRC channel #fuchsia on Freenode.

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.