[roll] Roll fuchsia [starnix] Enable Futex PI for Binder

Avoid fidl calls to RoleManager by using futex PI to directly apply a
thread profile.

When we are the sender of a binder transaction, we now track the zircon
handle of the receiver. When we continue on to block waiting for a
response, this allows us to pass the handle to the futex we are blocking
on to arrange for priority inheritance.

In this patch, we only arrange for futex PI if we know the target
thread from an existing transaction. Unfortunately, that's only when we
are sending-and-blocking in response to request,
e.g. (A -> B -pi-> A -pi-> B -> A)

Original-Bug: 401258133

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1430817
Original-Revision: a212b96e6912c356d31d17374391a48e97ac4af8
GitOrigin-RevId: 8c24e57f95a63dfaf6b555f5c95cab36f3b170a6
Change-Id: Ia1d0c5f9fb039f162a1dc7846e9f40085537184a
1 file changed
tree: a4ea410b8d86d1058065ac0d761655dde0de6299
  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.