Begin moving away code from ReadBuffers()

ReadBuffers() roughly does the following:
1. Checks preconditions
2. Optionally emits metadata trace packets
3. Reads the buffers into trace packets
4. Optionally emits more metadata trace packets
5. Writes into file/sends to IPC
6. Schedules more tasks

This commits moves the code of step 1 to the callers: the preconditions
that need to be checked are very different based on the caller.

No functional change.

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