summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorVincent Donnefort <vdonnefort@google.com>2024-02-20 23:23:07 +0300
committerSteven Rostedt (Google) <rostedt@goodmis.org>2024-03-18 17:12:47 +0300
commit180e4e390978af9d0cc060e87920c462276453b9 (patch)
treeef13bfaaa3fd1823bc8fc0969866e951c0975e33 /tools/perf/scripts/python/export-to-postgresql.py
parentb70f2938242a028f8e9473781ede175486a59dc8 (diff)
downloadlinux-180e4e390978af9d0cc060e87920c462276453b9.tar.xz
tracing: Add snapshot refcount
When a ring-buffer is memory mapped by user-space, no trace or ring-buffer swap is possible. This means the snapshot feature is mutually exclusive with the memory mapping. Having a refcount on snapshot users will help to know if a mapping is possible or not. Instead of relying on the global trace_types_lock, a new spinlock is introduced to serialize accesses to trace_array->snapshot. This intends to allow access to that variable in a context where the mmap lock is already held. Link: https://lore.kernel.org/linux-trace-kernel/20240220202310.2489614-4-vdonnefort@google.com Signed-off-by: Vincent Donnefort <vdonnefort@google.com> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions