[roll] Roll fuchsia [kernel][vm] Eviction and page request tracepoints

Add more arguments to existing page_request_* trace durations.
These now have four arguments:
 - vmo_id: koid of the VMO
 - offset: start offset of the request
 - length: length of the request
 - type: whether this is a READ or DIRTY request for page reads and
   writes respectively
The most relevant duration here is page_request_wait which tracks how
long a thread is blocked on a page request.

Add an evict_page duration for page eviction. This has three arguments:
 - vmo_id: koid of the VMO
 - offset: offset of the page being evicted
 - vmo_name: ZX_PROP_NAME of the VMO if set
The vmo_id and offset will help match with the page request events.

These trace points can be enabled with the vm_tracing_level=1 build
argument and collected with the kernel:vm category.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1278605
Original-Revision: 2eae24f747e860beb23236f66cf0f40fe8a4c339
GitOrigin-RevId: 9a404ccc39cff0efd54b8836b5cd431bf2e882b3
Change-Id: Ib1095a7519b4e29c83565df14412049533d692ac
1 file changed
tree: 5e9d241f3e1b0d0afa38b7f563572c0ca516f6cf
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.