[roll] Roll fuchsia [starnix] Avoid code injection on module changes

In restricted executor, since the Linux thread and the starnix kernel
are running in the same Zircon thread, it's possible to issue a software
breakpoint in the starnix kernel directly to notify a module change.
This uses less hack and results in a cleaner code.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/858017
Original-Revision: 3d0f21f45edcb8e7eec4136034b75eb40d07dece
GitOrigin-RevId: f8a02bbf457e1e83a83804392494698a9b0ce1bd
Change-Id: I7e2c7dda51dc71fc645d92675f8ceb2838f63912
1 file changed
tree: 43c0422cbd7c669be520a59f016f48920cf0231e
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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 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.