Google Git
Sign in
flutter / third_party / perfetto / 56bc0c6ea56325b6f5ba2225e6b1f27f5a5eb978
commit56bc0c6ea56325b6f5ba2225e6b1f27f5a5eb978[log] [tgz]
authorRyan Savitski <rsavitski@google.com>Mon Jan 27 13:50:02 2020 +0000
committerRyan Savitski <rsavitski@google.com>Mon Jan 27 13:50:02 2020 +0000
tree9db589ea29c20d20c9f07de5f9eab1710dc2047e
parent5e2dbac05619598f7aee7a0e4bcbd5c11798a4ec [diff]
traced_perf: re-enable linux build + add x86 regs handling

We need the kernel UAPI headers for the perf regs enums, I'm sourcing
them from buildtools/bionic, as with the in-tree builds.

I've previously promised to look into explicit reassignments instead of
memcpy/loop for arm/arm64, but ended up keeping them, as there's no
really sensible enum to index the "user" regs by (I'm not exactly sure
whether MachineArm64.h is the conceptually right enum either, but that's
what's used in practice, and all of these layouts match anyway).

Bug: 144281346
Change-Id: Id4a388e3772ce10b0f8aa43b6a30f8f43e91c93d
7 files changed
tree: 9db589ea29c20d20c9f07de5f9eab1710dc2047e
  1. bazel/
  2. build_overrides/
  3. buildtools/
  4. debian/
  5. docs/
  6. gn/
  7. include/
  8. infra/
  9. protos/
  10. src/
  11. test/
  12. tools/
  13. ui/
  14. .clang-format
  15. .gitignore
  16. .gn
  17. .style.yapf
  18. Android.bp
  19. Android.bp.extras
  20. BUILD
  21. BUILD.extras
  22. BUILD.gn
  23. codereview.settings
  24. heapprofd.rc
  25. LICENSE
  26. MODULE_LICENSE_APACHE2
  27. NOTICE
  28. OWNERS
  29. perfetto.rc
  30. PRESUBMIT.py
  31. README.chromium
  32. README.md
  33. TEST_MAPPING
  34. WORKSPACE
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Contributing

See /docs/contributing.md for instructions.

The source-of-truth repo is Android's Gerrit. The GitHub repo is a read-only mirror.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.

Community

You can reach us on our Discord channel. If you prefer using IRC we have an experimental Discord <> IRC bridge synced with #perfetto-dev on Freenode.