Linux Trace Users

• Thread Index

• [RELEASE] LTTng-modules 2.12.19 and 2.13.16 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.15 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng 2.12.16 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.14 - NordicitéE
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.14 and 2.12.18 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] DTrace 2.0.1
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• Common Trace Format 2 (CTF2) specification and sub-specs
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.13 and 2.12.17 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Ftrace, KASLR and gdb
  • From: alexandre.ferrieux@xxxxxxxxxx
• Re: Ftrace, KASLR and gdb
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Ftrace, KASLR and gdb
  • From: alexandre.ferrieux@xxxxxxxxxx
• Re: Ftrace, KASLR and gdb
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Ftrace, KASLR and gdb
  • From: alexandre.ferrieux@xxxxxxxxxx
• Re: Cannot build KernelShark on Ubuntu 22.04
  • From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
• Re: Cannot build KernelShark on Ubuntu 22.04
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• Re: Cannot build KernelShark on Ubuntu 22.04
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• Re: Cannot build KernelShark on Ubuntu 22.04
  • From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
• Re: Cannot build KernelShark on Ubuntu 22.04
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• Cannot build KernelShark on Ubuntu 22.04
  • From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
• Re: Beginner question about KernelShark
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Fwd: Beginner question about KernelShark
  • From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
• [ANNOUNCE] uftrace v0.16 is released
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• [RELEASE] LTTng-UST 2.12.10 and 2.13.8 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: RFC: using NIC DMA ring as tracing buffer?
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• Re: RFC: using NIC DMA ring as tracing buffer?
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• Re: RFC: using NIC DMA ring as tracing buffer?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• RFC: using NIC DMA ring as tracing buffer?
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.13 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] DTrace 2.0.0-1.14
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [RELEASE] LTTng 2.12.15 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.12 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.6 - Amqui
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Fwd: [lttng-dev] [CTF2-SPEC-2.0] Announcing CTF 2, the next generation of the Common Trace Format
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.16 and 2.13.12 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• user-space rtla vs kernel tracing dependency?
  • From: Leon Woestenberg <leon@xxxxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.15 and 2.13.11 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.12.9 and 2.13.7 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [ANNOUNCE] uftrace v0.15 is released!
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: Steven Rostedt <rostedt@xxxxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: Steven Rostedt <rostedt@xxxxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: David Vernet <void@xxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: David Vernet <void@xxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] trace-cmd record: Reset PATH variable after strtok search
  • From: David Vernet <void@xxxxxxxxxxxxx>
• Re: This list is being migrated to new infrastructure
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• This list is being migrated to new infrastructure
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.11 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: How to solve the coupling between libtraceevent and kernel trace?
  • From: Lv Ying <lvying6@xxxxxxxxxx>
• Re: How to solve the coupling between libtraceevent and kernel trace?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: How to solve the coupling between libtraceevent and kernel trace?
  • From: Lv Ying <lvying6@xxxxxxxxxx>
• Re: How to solve the coupling between libtraceevent and kernel trace?
  • From: Lv Ying <lvying6@xxxxxxxxxx>
• Re: How to solve the coupling between libtraceevent and kernel trace?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• How to solve the coupling between libtraceevent and kernel trace?
  • From: Lv Ying <lvying6@xxxxxxxxxx>
• Re: [Issue of trace-cmd] undefined symbol when import ctracecmd.so in python
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Issue of trace-cmd] undefined symbol when import ctracecmd.so in python
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: cannot run trace-cmd split in parallel
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: cannot run trace-cmd split in parallel
  • From: Sharon Gabay <Sharon.Gabay@xxxxxxxxxxxx>
• cannot run trace-cmd split in parallel
  • From: Sharon Gabay <Sharon.Gabay@xxxxxxxxxxxx>
• [RELEASE] DTrace 2.0.0-1.13.1
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.14 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.10 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [ANNOUNCE] uftrace v0.14 is out!
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• libtracecmd-rs: Rust wrapper for libtracecmd - now released!
  • From: Keiichi Watanabe <keiichiw@xxxxxxxxxx>
• Tracing Summit - Last year's 2022 talk recordings are available online!
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [ANNOUNCE] libtraceevent 1.7.3 is released
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtracefs v1.7 is released
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtracecmd v1.4 is released
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] trace-cmd v3.2 is released
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] LTTng UST 2.12.8/2.13.6 and LTTng modules 2.12.14/2.13.10 tracers
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.5 - Amqui
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Trying to trace when RT FF & RR threads hit RT Throttle limit (kernel.sched_rt_runtime_us)
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: CSV output
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: CSV output
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• [RELEASE] DTrace 2.0.0-1.12
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• Re: CSV output
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: CSV output
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: CSV output
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: CSV output
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: CSV output
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• CSV output
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• [PATCH] libtraceevent: fix make test on big endian architectures
  • From: Lucas Kanashiro <kanashiro@xxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.13 and 2.13.9 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: About rtla osnoise and timerlat usage
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.12 and 2.13.8 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [ANNOUNCE] uftrace v0.13 is released!
  • From: Namhyung Kim <namhyung@xxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.13 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.9 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [ANNOUNCE] trace-cruncher 0.3.0 (beta)
  • From: Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx>
• Re: kernelshark: Proper way to install documents when packaging as rpm
  • From: Zamir SUN <sztsian@xxxxxxxxx>
• Re: kernelshark: Proper way to install documents when packaging as rpm
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• kernelshark: Proper way to install documents when packaging as rpm
  • From: Zamir SUN <sztsian@xxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.7, 2.12.11 and LTTng-UST 2.13.5, 2.12.7
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: trace-cmd: Using the python wrapping to read trace markers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace-cmd: Using the python wrapping to read trace markers
  • From: Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx>
• trace-cmd: Using the python wrapping to read trace markers
  • From: Sharon Gabay <Sharon.Gabay@xxxxxxxxxxxx>
• Re: Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• RE: Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• RE: Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• Kernelshark: funcgraph_exit events don't seem to exit?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• RE: `fungraph_entry` and `funcgraph_exit` entries: is there a mismatch between trace-cmd and the format of debugfs?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: libtraceevent -- undefined functions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: libtraceevent -- undefined functions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: libtraceevent -- undefined functions
  • From: Michael Petlan <mpetlan@xxxxxxxxxx>
• Re: libtraceevent -- undefined functions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: `fungraph_entry` and `funcgraph_exit` entries: is there a mismatch between trace-cmd and the format of debugfs?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• `fungraph_entry` and `funcgraph_exit` entries: is there a mismatch between trace-cmd and the format of debugfs?
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: About tracing clues
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: About tracing clues
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.12 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.8 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: About tracing clues
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• [RELEASE] LTTng-ust 2.12.6 and 2.13.4 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.10 and 2.13.5 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: About tracing clues
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• About tracing clues
  • From: Prasad Pandit <ppandit@xxxxxxxxxx>
• Re: stream based live time synchronized tracing?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: stream based live time synchronized tracing?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• stream based live time synchronized tracing?
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• Re: Format of funcgraph_{entry, exit} ftrace event
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Format of funcgraph_{entry, exit} ftrace event
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Tracing Summit 2022: Announcement and Call for Proposals, October 11th - 13th, 2022, London, United Kingdom
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path
  • From: Daniel Wagner <dwagner@xxxxxxx>
• Re: [RFC v1] libtraceevent: Add initial support for meson
  • From: Daniel Wagner <dwagner@xxxxxxx>
• Re: [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC v1] libtraceevent: Add initial support for meson
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path
  • From: Daniel Wagner <dwagner@xxxxxxx>
• [RFC v1] libtraceevent: Add initial support for meson
  • From: Daniel Wagner <dwagner@xxxxxxx>
• [RFC v1 2/2] libtracefs: Add initial support for meson
  • From: Daniel Wagner <dwagner@xxxxxxx>
• Re: Having difficulty trying to cross-compile latest trace-cmd
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Having difficulty trying to cross-compile latest trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Having difficulty trying to cross-compile latest trace-cmd
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• RE: Format of trace.dat flyrecord section
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: Format of trace.dat flyrecord section
  • From: Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx>
• RE: Format of trace.dat flyrecord section
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• RE: Format of trace.dat flyrecord section
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• Re: Format of trace.dat flyrecord section
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Format of trace.dat flyrecord section
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Format of trace.dat flyrecord section
  • From: Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx>
• Format of trace.dat flyrecord section
  • From: Matteo Bertolino <matteo.bertolino@xxxxxxxxxx>
• ANNOUNCE: Linux Distributed Lock Manager Viewer
  • From: Alexander Aring <aahringo@xxxxxxxxxx>
• [RELEASE] DTrace 2.0.0-1.10
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [RELEASE] LTTng-UST 2.13.3 and 2.12.5 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.4 and 2.12.9 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v2] percpu: improve percpu_alloc_percpu event trace
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.11 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.7 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: arm64 execve/clone sys_exit tracepoints
  • From: Federico Di Pierro <nierro92@xxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.6 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.10 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.9 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.5 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.13.2 and 2.12.4 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.3 and 2.12.8 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: arm64 execve/clone sys_exit tracepoints
  • From: Federico Di Pierro <nierro92@xxxxxxxxx>
• [ANNOUNCE] trace-cmd 3.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: arm64 execve/clone sys_exit tracepoints
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• arm64 execve/clone sys_exit tracepoints
  • From: Federico Di Pierro <nierro92@xxxxxxxxx>
• [RELEASE] LTTng-modules 2.13.2 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [ANNOUNCE] libtracefs 1.3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtracefs 1.3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.8 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.4 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: [RELEASE] LTTng-UST 2.12.3 and 2.11.5 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.12.3 and 2.11.5 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.7 and 2.13.1 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.7 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.2 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.13.1 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [CORRECTED] RELEASE: DTrace for Linux 2.0.0-1.8
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• RELEASE: DTrace for Linux 2.0.0-1.7
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [RELEASE] LTTng-tools 2.13.1 - Nordicité
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.12.6 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.11.8 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• RELEASE: DTrace for Linux 2.0.0-1.7
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• CFP for Linux Plumbers Tracing microconference ends this Friday
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] LTTng 2.12.5 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• LTTng 2.13.0 - Nordicité - Linux kernel and user-space tracer
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [lttng-dev] [RELEASE] LTTng 2.13.0-rc3 - Nordicité - Linux kernel and user-space tracer
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [PATCH 4/4] libtraceevent: Increase libtraceevent logging when verbose
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• [PATCH 3/4] perf: Add define for libtracefs version
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• [PATCH 2/4] perf: Add define for libtraceevent version
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• [PATCH 1/4] perf: Enable libtracefs dynamic linking
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• Re: [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC PATCH] libtraceevent: Increase libtraceevent logging when verbose
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• [RELEASE] LTTng 2.12.4 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.11.7 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [ANNOUNCE] KernelShark 2.0
  • From: Yordan Karadzhov <y.karadz@xxxxxxxxx>
• [RELEASE] LTTng 2.13.0-rc2 - Nordicité - Linux kernel and user-space tracer
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: [RELEASE] LTTng-modules 2.11.9 and 2.12.6 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.9 and 2.12.6 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.11.4 and 2.12.2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: how to continuously capture events
  • From: Lin Wang <wanglinseven@xxxxxxxxx>
• Re: how to continuously capture events
  • From: Lin Wang <wanglinseven@xxxxxxxxx>
• Re: how to continuously capture events
  • From: Jonathan Rajotte-Julien <jonathan.rajotte-julien@xxxxxxxxxxxx>
• Re: how to continuously capture events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• how to continuously capture events
  • From: Lin Wang <wanglinseven@xxxxxxxxx>
• [RELEASE] LTTng 2.13.0-rc1 - Nordicité - Linux kernel and user-space tracer
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• RELEASE: DTrace for Linux 2.0.0-1.5
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [ANNOUNCE] libtracececmd 1.0.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtracefs 1.1.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtraceevent 1.2.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] KernelShark 1.3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] trace-cmd 2.9.2
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.11.6 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng 2.12.3 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• lttng-trace: a new strace-alike LTTng command
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.8 and 2.12.5 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.11.3 and 2.12.1 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.7 and 2.12.4 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [ANNOUNCE] libtracefs 1.0.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] libtraceevent 1.1.1
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RELEASE: New version of DTrace for Linux
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [ANNOUNCE] libtracefs.git
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RELEASE: New version of DTrace for Linux
  • From: Kris Van Hees <kris.van.hees@xxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.3 and 2.11.6 (Linux kernel tracer) (security fix)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: function_profile_enabled not showing Time info
  • From: Ahmed Zaki <anzaki@xxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.5 and 2.12.2 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng 2.12.2 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.11.5 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [ANNOUNCE] trace-cmd 2.9
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [lttng-dev] Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: [lttng-dev] Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: [lttng-dev] Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: [lttng-dev] Capturing User-Level Function Calls/Returns
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: [lttng-dev] Capturing User-Level Function Calls/Returns
  • From: Michel Dagenais <michel.dagenais@xxxxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Capturing User-Level Function Calls/Returns
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Capturing User-Level Function Calls/Returns
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Sp! Re: Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Sp! Re: Perf Script Erroneous User Stack Trace
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Sp! Re: Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Sp! Re: Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Perf Script Erroneous User Stack Trace
  • From: Ian Rogers <irogers@xxxxxxxxxx>
• Re: Perf Script Erroneous User Stack Trace
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Perf Script Erroneous User Stack Trace
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [RELEASE] LTTng-modules 2.12.1 and 2.11.4 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Perf Reports Jump Instructions as Memory Access Instructions
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [RELEASE] LTTng-tools 2.11.4 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Perf Reports Jump Instructions as Memory Access Instructions
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [RELEASE] LTTng 2.12.1 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.9.15 - Joannès
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-tools 2.11.3 - Lafontaine
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [RELEASE] LTTng 2.12.0 - (Ta) Meilleure (Linux kernel and user space tracer)
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.11.2 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.10.5 and 2.11.3 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: debuginfod-based dwarf downloading, was Re: Wrong Perf Backtraces
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: debuginfod-based dwarf downloading, was Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• debuginfod-based dwarf downloading, was Re: Wrong Perf Backtraces
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [RELEASE] LTTng 2.12-rc3 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [RELEASE] LTTng-modules and LTTng-UST 2.12.0-rc3 (International Stay At Home Month)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Milian Wolff <milian.wolff@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• [PATCH] ftrace/kprobe: Show the maxactive number on kprobe_events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: How to recheck 'maxactive' ?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: How to recheck 'maxactive' ?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: How to recheck 'maxactive' ?
  • From: Taeung Song <treeze.taeung@xxxxxxxxx>
• Re: Re: Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: How to recheck 'maxactive' ?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: Wrong Perf Backtraces
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Wrong Perf Backtraces
  • From: ahmadkhorrami <ahmadkhorrami@xxxxxxxx>
• How to recheck 'maxactive' ?
  • From: Taeung Song <treeze.taeung@xxxxxxxxx>
• [RELEASE] LTTng-UST 2.10.7, 2.11.1, 2.12.0-rc2 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.12.0-rc2, 2.11.2, 2.10.14 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng 2.12-rc1 - (Ta) Meilleure
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.10.13 and 2.11.1 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.0
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• Re: register_jprobe always fails with -22
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: register_jprobe always fails with -22
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.0-rc4
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.0-rc2
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng 2.11.0 - Lafontaine (Linux kernel and user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] Babeltrace 2.0.0-rc1
  • From: Jérémie Galarneau <jeremie.galarneau@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.9.15 (EOL), 2.10.12 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.9.7 (EOL), 2.10.6 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.0-rc7 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST 2.11.0-rc5 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-modules 2.11.0-rc6, 2.10.11, 2.9.14 (Linux kernel tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RELEASE] LTTng-UST v2.11.0-rc4, v2.10.5, v2.9.6 (Linux user-space tracer)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Tracing Summit 2019 - Schedule Release
  • From: Francis Deslauriers <francis.deslauriers@xxxxxxxxxxxx>
• Re: [ANNOUNCE] KernelShark 1.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] KernelShark 1.0
  • From: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx>
• [ANNOUNCE] KernelShark 1.0
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Submit to the Tracing Microconference at Linux Plumbers 2019
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] trace-cmd v2.8.1
  • From: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx>
• [ANNOUNCE] trace-cmd v2.8.1
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: register_jprobe always fails with -22
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• register_jprobe always fails with -22
  • From: Naruto Nguyen <narutonguyen2018@xxxxxxxxx>
• Re: increase size of number of possible tracing events
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: increase size of number of possible tracing events
  • From: Anthony Eden <aeden@xxxxxxxxxxxxx>
• Re: increase size of number of possible tracing events
  • From: Anthony Eden <aeden@xxxxxxxxxxxxx>
• Re: increase size of number of possible tracing events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: increase size of number of possible tracing events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• increase size of number of possible tracing events
  • From: Anthony Eden <aeden@xxxxxxxxxxxxx>
• Re: How to find out which process cause a strange increasing cpu load on a certain core?
  • From: Naruto Nguyen <narutonguyen2018@xxxxxxxxx>
• Re: How to find out which process cause a strange increasing cpu load on a certain core?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• How to find out which process cause a strange increasing cpu load on a certain core?
  • From: Naruto Nguyen <narutonguyen2018@xxxxxxxxx>
• Re: [ANNOUNCE] trace-cmd v2.8
  • From: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx>
• Re: Trace event filtering
  • From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
• Re: Trace event filtering
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Trace event filtering
  • From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
• [ANNOUNCE] trace-cmd v2.8
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] Last chance to vote for a logo for KernelShark
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Missing exceptions:page_fault_user event?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Missing exceptions:page_fault_user event?
  • From: Trip Volpe <trip.volpe@xxxxxxxxx>
• Re: Missing exceptions:page_fault_user event?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Missing exceptions:page_fault_user event?
  • From: Trip Volpe <trip.volpe@xxxxxxxxx>
• Re: Is it probably to trigger function graph via trace event?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Is it probably to trigger function graph via trace event?
  • From: wyang <w90p710@xxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH v7 16/16] perf-probe: Add array argument support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 15/16] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 14/16] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 13/16] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 12/16] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 11/16] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 10/16] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 09/16] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 08/16] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 07/16] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 06/16] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 05/16] tracing: probeevent: Unify fetch type tables
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 04/16] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 03/16] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 02/16] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 01/16] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v6 10/21] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v6 10/21] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v6 21/21] perf-probe: Add array argument support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v6 04/21] selftests: ftrace: Add a testcase for probepoint
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v6 21/21] perf-probe: Add array argument support
  • From: Ravi Bangoria <ravi.bangoria@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 21/21] perf-probe: Add array argument support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: perf probe resolving different symbol?
  • From: Nick Kirsch <nick@xxxxxxxxxx>
• Re: [GIT PULL 00/14] perf/core improvements and fixes
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• [GIT PULL 00/14] perf/core improvements and fixes
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• [PATCH 12/14] perf probe: Use right type to access array elements
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: [PATCH v6 21/21] perf-probe: Add array argument support
  • From: Ravi Bangoria <ravi.bangoria@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 00/21] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 21/21] perf-probe: Add array argument support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 20/21] [RESEND] perf-probe: Fix to convert array type collectly
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 19/21] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 18/21] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 17/21] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 16/21] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 15/21] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 14/21] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 13/21] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 12/21] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 11/21] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 10/21] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 09/21] tracing: probeevent: Unify fetch type tables
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 08/21] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 07/21] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 06/21] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 04/21] selftests: ftrace: Add a testcase for probepoint
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 03/21] selftests: ftrace: Add a testcase for string type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 02/21] selftests: ftrace: Add probe event argument syntax testcase
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 01/21] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v6 00/21] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: perf probe resolving different symbol?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: perf probe resolving different symbol?
  • From: Masami Hiramatsu <masami.hiramatsu@xxxxxxxxx>
• Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: perf probe resolving different symbol?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• perf probe resolving different symbol?
  • From: Nick Kirsch <nick@xxxxxxxxxx>
• Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Ravi Bangoria <ravi.bangoria@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Ravi Bangoria <ravi.bangoria@xxxxxxxxxxxxxxxxxx>
• [PATCH v5 19/19] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 17/19] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 16/19] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 15/19] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 14/19] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 13/19] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 12/19] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 11/19] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 10/19] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 09/19] tracing: probeevent: Unify fetch type tables
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 08/19] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 07/19] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 06/19] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 05/19] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 04/19] selftests: ftrace: Add a testcase for probepoint
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 03/19] selftests: ftrace: Add a testcase for string type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 02/19] selftests: ftrace: Add probe event argument syntax testcase
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v5 00/19] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v4 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v4 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH v4 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v4 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v4 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH v4 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH v4 15/19] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 19/19] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 17/19] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 16/19] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 14/19] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 13/19] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 12/19] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 11/19] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 10/19] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 09/19] tracing: probeevent: Unify fetch type tables
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 08/19] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 07/19] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 06/19] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 05/19] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 04/19] selftests: ftrace: Add a testcase for probepoint
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 03/19] selftests: ftrace: Add a testcase for string type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 02/19] selftests: ftrace: Add probe event argument syntax testcase
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v4 00/19] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v3 15/18] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v3 15/18] tracing: probeevent: Add array type support
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH v3 18/18] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 17/18] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 16/18] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 15/18] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 14/18] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 13/18] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 12/18] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 11/18] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 10/18] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 09/18] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 08/18] tracing: probeevent: Unify fetch type tables
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 07/18] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 06/18] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 05/18] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 04/18] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 03/18] selftests: ftrace: Add a testcase for string type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 02/18] selftests: ftrace: Add probe event argument syntax testcase
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v3 00/18] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [BUGFIX PATCH v2.1] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v2 07/17] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v2 07/17] tracing: probeevent: Introduce new argument fetching code
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [BUGFIX PATCH v2.1] tracing: probeevent: Fix to support minus offset from symbol
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH v2 15/17] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [BUGFIX PATCH v2.1] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v2 13/17] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 17/17] selftests: ftrace: Add a testcase for array type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 16/17] selftests: ftrace: Add a testcase for $argN with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 15/17] selftests: ftrace: Add a testcase for symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 14/17] tracing: probeevent: Add array type support
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 13/17] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 12/17] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 11/17] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 10/17] tracing: probeevent: Unify fetch_insn processing common part
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 09/17] tracing: probeevent: Append traceprobe_ for exported function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 08/17] tracing: probeevent: Return consumed bytes of dynamic area
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 07/17] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 06/17] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 05/17] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 04/17] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 03/17] selftests: ftrace: Add a testcase for string type with kprobe_event
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 02/17] selftests: ftrace: Add probe event argument syntax testcase
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH v2 00/17] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [RFC PATCH 0/8] tracing: probeevent: Improve fetcharg features
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC PATCH 7/8] tracing: probeevent: Add $argN for accessing function args
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 8/8] tracing: probeevent: Add an array for basic types
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 3/8] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 6/8] x86: ptrace: Add function argument access API
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 4/8] tracing: probeevent: Introduce new argument fetching code
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 5/8] tracing: probeevent: Add symbol type
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 2/8] tracing: probeevent: Cleanup argument field definition
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 1/8] tracing: probeevent: Cleanup print argument functions
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [RFC PATCH 0/8] tracing: probeevent: Improve fetcharg features
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 11/20 v2] tracing: Add symbol type to function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 15/18] tracing: Add string type for dynamic strings in function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 15/18] tracing: Add string type for dynamic strings in function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 13/18] tracing: Add array type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 13/18] tracing: Add array type to function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 09/18] tracing: Add indexing of arguments for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 09/18] tracing: Add indexing of arguments for function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 11/20 v2] tracing: Add symbol type to function based events
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: [PATCH 11/20 v2] tracing: Add symbol type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 01/20 v2] tracing: Add function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 11/18] tracing: Add symbol type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 09/18] tracing: Add indexing of arguments for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 03/18] tracing: Add simple arguments to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 11/20 v2] tracing: Add symbol type to function based events
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [PATCH 01/20 v2] tracing: Add function based events
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [PATCH 11/18] tracing: Add symbol type to function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 09/18] tracing: Add indexing of arguments for function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 03/18] tracing: Add simple arguments to function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH 03/20 v2] tracing: Add simple arguments to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 05/20 v2] tracing: Add hex print for dynamic ftrace based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 08/20 v2] tracing: Add "unsigned" to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 07/20 v2] tracing: Add dereferencing multiple fields per arg
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 06/20 v2] tracing: Add indirect offset to args of ftrace based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 04/20 v2] tracing/x86: Add arch_get_func_args() function
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 10/20 v2] tracing: Make func_type enums for easier comparing of arg types
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 09/20 v2] tracing: Add indexing of arguments for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 14/20 v2] tracing: Have char arrays be strings for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 11/20 v2] tracing: Add symbol type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 12/20 v2] tracing: Add accessing direct address from function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 17/20 v2] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 15/20 v2] tracing: Add string type for dynamic strings in function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 13/20 v2] tracing: Add array type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 01/20 v2] tracing: Add function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 20/20 v2] tracing: Add argument error message too many args for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 19/20 v2] tracing: Add error messages for failed writes to function_events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 18/20 v2] tracing/perf: Allow perf to use function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 16/20 v2] tracing: Add NULL to skip args for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 02/20 v2] tracing: Add documentation for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 00/20 v2] tracing: Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 01/18] tracing: Add function based events
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [PATCH 01/18] tracing: Add function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 01/18] tracing: Add function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Juri Lelli <juri.lelli@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Juri Lelli <juri.lelli@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 01/18] tracing: Add function based events
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>