commit | dea799ba7ccfd2cc5f359b9c1abb79b8cc1d9486 | [log] [tgz] |
---|---|---|
author | Ryan Savitski <rsavitski@google.com> | Tue Feb 11 22:13:12 2020 +0000 |
committer | Ryan Savitski <rsavitski@google.com> | Tue Feb 11 22:13:12 2020 +0000 |
tree | 3027e8e199d4f5c0926476e3a50b7acf2af6d8c0 | |
parent | 53df6ccf10cf10dd9f7c6dc2156cc8552092fd51 [diff] |
traced_perf: record presence of ring buffer data loss in the trace As mentioned in the comments, this wouldn't be particularly useful if we wanted to give precise time bounds of "when" the loss happened (as the loss is relative to a given ring buffer's contents). But I believe that it's sufficient for now to distinguish that a given cpu had "some" loss (since a typical trace should have no ring buffer loss). Bug: 144281346 Change-Id: Iadd8d67a724caa45d6b032744534818b3f0f6cfa
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.
See /docs/contributing.md for instructions.
The source-of-truth repo is Android's Gerrit. The GitHub repo is a read-only mirror.
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.