processor: Import chrome metadata / raw system traces with timestamps

Previously we were importing these into the raw events table with ts 0,
which would screw up the trace bounds calculation. We can use any
reasonable timestamp for these rows in the raw table, so we're choosing
the last packet timestamp seen by the tokenizer. This should work fine
since metadata and raw system traces usually appear at the end of
chrome traces.

Change-Id: Idf5acd2916ebe3a0aa47e88439abb560b957c332
3 files changed
tree: 235c80d72c68b5340ab98e0fbde618992121d4a1
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. Android.bp
  17. Android.bp.extras
  18. BUILD
  19. BUILD.extras
  20. BUILD.gn
  21. codereview.settings
  22. heapprofd.rc
  23. MODULE_LICENSE_APACHE2
  24. NOTICE
  25. OWNERS
  26. perfetto.rc
  27. PRESUBMIT.py
  28. README.chromium
  29. README.md
  30. TEST_MAPPING
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.

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.