Google Git
Sign in
flutter / third_party / perfetto / 09548772b3ac3f7349251b169754deec8fd60904
commit09548772b3ac3f7349251b169754deec8fd60904[log] [tgz]
authorNikita Ioffe <ioffe@google.com>Fri Mar 10 12:39:37 2023 +0000
committerNikita Ioffe <ioffe@google.com>Fri Mar 10 12:39:37 2023 +0000
treed0e3d92b2b2196bbbe623c1c2d436421df5a916e
parentf90d61c166b857309dcbc12e5a7c328578e5bd51 [diff]
Add support for hyp events in perfetto cmd

So far we only add basic support for "hyp" category, which will result
in the following ftrace config to collect all known hyp events:
```
instance_name: "hyp"
ftrace_events: "hyp/*"
```

If needed, in the future we can add support for only tracing specific
hypervisor events.

Bug: 249050813
Test: perfetto_unittests
Change-Id: I1c303e6312a7eb36083cf38488bfe98a813f4363
2 files changed
tree: d0e3d92b2b2196bbbe623c1c2d436421df5a916e
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. python/
  13. src/
  14. test/
  15. tools/
  16. ui/
  17. .clang-format
  18. .clang-tidy
  19. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gn
  23. .style.yapf
  24. Android.bp
  25. Android.bp.extras
  26. BUILD
  27. BUILD.extras
  28. BUILD.gn
  29. CHANGELOG
  30. codereview.settings
  31. DIR_METADATA
  32. heapprofd.rc
  33. LICENSE
  34. meson.build
  35. METADATA
  36. MODULE_LICENSE_APACHE2
  37. OWNERS
  38. perfetto.rc
  39. PerfettoIntegrationTests.xml
  40. PRESUBMIT.py
  41. README.chromium
  42. README.md
  43. TEST_MAPPING
  44. traced_perf.rc
  45. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.