diff options
| author | Masami Hiramatsu (Google) <mhiramat@kernel.org> | 2026-07-28 21:49:51 +0900 |
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2026-07-29 14:27:55 -0400 |
| commit | c786d2bdf1f3964deee192ad942dee2a741c1e2c (patch) | |
| tree | 7b437e14baee8aa82e0c3a541f4c2b9027aa776a /tools/perf/scripts/python/syscall-counts.py | |
| parent | f5098b6bae761e346ebcd9da7f95622c04733cff (diff) | |
tracing/mmiotrace: Reset dropped_count in mmio_reset_data()
mmio_reset_data() is called during tracer initialization, reset, and
start. While it resets overrun_detected and prev_overruns, it neglects
to reset dropped_count. Consequently, dropped event counts from prior
tracing sessions persist in dropped_count and corrupt overrun reports
in subsequent runs.
Fix this by explicitly calling atomic_set(&dropped_count, 0) in
mmio_reset_data().
Link: https://patch.msgid.link/178524299122.56416.16277704230639425172.stgit@devnote2
Fixes: 173ed24ee2d6 ("mmiotrace: count events lost due to not recording")
Assisted-by: Antigravity:gemini-3.6-flash
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions