[roll] Roll fuchsia [zircon] Actually migrate dpcs to the new CPU

Fixes a typo in the dpc migration logic. We should be migrating into the
current DpcRunner rather from the source into itself.

Additionally, if we transitioned dpcs, signal the dpc queues so they
don't need to wait until the next dpc arrives.

Original-Bug: 511205186
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1606915
Original-Revision: 98b467194397df8a0d31f2e6aa708e49e2f38e8b
GitOrigin-RevId: d7f7fdb6a4da30111dc818c948dbcfcaf6510c5b
Change-Id: I2d1fbc014b3dada358fd21ecb6093e2cc003be21
1 file changed
tree: 00472684f303d47051feaa09c87e282e42764ec9
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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 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.