Linux Trace Users

• Thread Index

• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 13/18] tracing: Add array type to function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Namhyung Kim <namhyung@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: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• 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: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• 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: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 13/18] tracing: Add array type to 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 13/18] tracing: Add array type to function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• [PATCH 07/18] tracing: Add dereferencing multiple fields per arg
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 04/18] tracing/x86: Add arch_get_func_args() function
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 06/18] tracing: Add indirect offset to args of ftrace based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 15/18] tracing: Add string type for dynamic strings in function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 10/18] tracing: Make func_type enums for easier comparing of arg types
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 08/18] tracing: Add "unsigned" to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 09/18] tracing: Add indexing of arguments for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 11/18] tracing: Add symbol type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 12/18] tracing: Add accessing direct address from function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 14/18] tracing: Have char arrays be strings for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 13/18] tracing: Add array type to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 17/18] tracing: Add indirect to indirect access for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 16/18] tracing: Add NULL to skip args for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 18/18] tracing/perf: Allow perf to use function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 03/18] tracing: Add simple arguments to function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 05/18] tracing: Add hex print for dynamic ftrace based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 02/18] tracing: Add documentation for function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 00/18] [ANNOUNCE] Dynamically created function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 01/18] tracing: Add function based events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] trace-cmd v2.7
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Missing Events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Missing Events
  • From: Michael Sartain <mikesart@xxxxxxxxxxxx>
• [ANNOUNCE] trace-cmd 2.6.1
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frantisek Rysanek" <Frantisek.Rysanek@xxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frantisek Rysanek" <Frantisek.Rysanek@xxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frantisek Rysanek" <Frantisek.Rysanek@xxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• noob q.: trying to trace syscalls in Jessie... why do I get unselected "events" in the trace?
  • From: "Frantisek Rysanek" <Frantisek.Rysanek@xxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• RE: Why return probes of some syscalls sometimes are not called?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• RE: Why return probes of some syscalls sometimes are not called?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• RE: Why return probes of some syscalls sometimes are not called?
  • From: "Chernookyi, Vitalii" <vitalii.chernookyi@xxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Why return probes of some syscalls sometimes are not called?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Why return probes of some syscalls sometimes are not called?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Why return probes of some syscalls sometimes are not called?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children
  • From: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 3/4] tracing: Add infrastructure to allow set_event_pid to follow children
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [RFC][PATCH 3/4] tracing: Add infrastructure to allow set_event_pid to follow children
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH 3/4] tracing: Add infrastructure to allow set_event_pid to follow children
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC][PATCH 1/4] tracing: Rename check_ignore_pid() to ignore_this_task()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC][PATCH 3/4] tracing: Add infrastructure to allow set_event_pid to follow children
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC][PATCH 4/4] tracing: Update the documentation to describe "event-fork" option
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Peter Xu <peterx@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Peter Xu <peterx@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Luiz Capitulino <lcapitulino@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Peter Xu <peterx@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Peter Xu <peterx@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Qemu-devel] [RFC] host and guest kernel trace merging
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• [RFC] host and guest kernel trace merging
  • From: Luiz Capitulino <lcapitulino@xxxxxxxxxx>
• Re: stacktrace on 4.4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: stacktrace on 4.4
  • From: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
• Re: stacktrace on 4.4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: stacktrace on 4.4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• stacktrace on 4.4
  • From: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
• Re: are tracepoints lossy?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: are tracepoints lossy?
  • From: "Kornievskaia, Olga" <Olga.Kornievskaia@xxxxxxxxxx>
• are tracepoints lossy?
  • From: "Kornievskaia, Olga" <Olga.Kornievskaia@xxxxxxxxxx>
• [ANNOUNCE] trace-cmd 2.6
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] trace-cmd 2.5.2 (and others)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [ANNOUNCE] trace-cmd 2.5.2 (and others)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH v3] trace-record: slow down trace_waitpid loop
  • From: Vincent Stehlé <vincent.stehle@xxxxxxxxxxxxx>
• Re: [PATCH v2] trace-record: slow down trace_waitpid loopi
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v2] trace-record: slow down trace_waitpid loopi
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH v2] trace-record: slow down trace_waitpid loop
  • From: Vincent Stehlé <vincent.stehle@xxxxxxxxxxxxx>
• Mailing list for performance events and tracing subsystems
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• [PATCH RFC] trace-record: slow down trace_waitpid loop
  • From: Vincent Stehlé <vincent.stehle@xxxxxxxxxxxxx>
• [ANNOUNCE] trace-cmd v2.5 released
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• function_graph with options/stacktrace
  • From: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
• Re: function profiling with set_ftrace_pid
  • From: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
• Re: function profiling with set_ftrace_pid
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• function profiling with set_ftrace_pid
  • From: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
• Re: tracing at start and end for some trace events
  • From: Yuyang Du <yuyang.du@xxxxxxxxx>
• Re: tracing at start and end for some trace events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: tracing at start and end for some trace events
  • From: Yuyang Du <yuyang.du@xxxxxxxxx>
• tracing at start and end for some trace events
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: How to dump trace buffer at boot stage
  • From: wyang <w90p710@xxxxxxxxx>
• Re: How to dump trace buffer at boot stage
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• How to dump trace buffer at boot stage
  • From: wyang <w90p710@xxxxxxxxx>
• Re: [PATCH] trace-input: init kbuf back to NULL after free kbuf
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] trace-input: init kbuf back to NULL after free kbuf
  • From: Ditang Chen <chendt.fnst@xxxxxxxxxxxxxx>
• Re: [PATCH] trace-input: init kbuf back to NULL after free kbuf
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] trace-input: init kbuf back to NULL after free kbuf
  • From: Ditang Chen <chendt.fnst@xxxxxxxxxxxxxx>
• Re: [PATCH] trace-input: Fix a memory double free
  • From: Ditang Chen <chendt.fnst@xxxxxxxxxxxxxx>
• Re: [PATCH] trace-input: Fix a memory double free
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] trace-input: Fix a memory double free
  • From: Chen Ditang <chendt.fnst@xxxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd: Fix out-of-tree build
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] trace-cmd: Fix out-of-tree build
  • From: Kusanagi Kouichi <slash@xxxxxxxxxxxxxxx>
• [PATCH 3/3] trace-cmd: Fix and cleanup kvm_nested_vmexit tracepoints
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• [PATCH 2/3] trace-cmd: Factor out print_exit_reason in kvm plugin
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• [PATCH 1/3] trace-cmd: Report unknown VMX exit reasons with code
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• [PATCH 0/3] trace-cmd: Updates for kvm plugin
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Query: is it possible to trace at exactly start and end time of tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Query: is it possible to trace at exactly start and end time of tracing
  • From: "Du, Yuyang" <yuyang.du@xxxxxxxxx>
• Re: Problem in loading a python plugin for trace-cmd tool
  • From: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx>
• Re: Problem in loading a python plugin for trace-cmd tool
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: Problem in loading a python plugin for trace-cmd tool
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Problem in loading a python plugin for trace-cmd tool
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Problem in loading a python plugin for trace-cmd tool
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 2/3] xhci: trace debug messages related to driver initialization and unload
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 3/3] xhci: trace debug statements related to ring expansion
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 1/3] xhci: trace debug statements for urb cancellation
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: [RFC 2/3] xhci: trace debug messages related to driver initialization and unload
  • From: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx>
• [RFC 3/3] xhci: trace debug statements related to ring expansion
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC 2/3] xhci: trace debug messages related to driver initialization and unload
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC 1/3] xhci: trace debug statements for urb cancellation
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx>
• Re: Help in enabling early boot tracing
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Help in enabling early boot tracing
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v3 4/4] xhci: add xhci_cmd_completion trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v3 3/4] xhci: add xhci_address_ctx trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v3 2/4] xhci: add trace for debug messages related to endpoint reset
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v3 1/4] xhci: add trace for debug messages related to quirks
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v5] xhci: add traces for debug messages in xhci_address_device()
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v3] xhci: add trace for debug messages related to changing contexts
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 3/4] xhci: add xhci_address_ctx trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 4/4] xhci: add xhci_cmd_completion trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 2/4] xhci: add trace for debug messages related to endpoint reset
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2 1/4] xhci: add trace for debug messages related to quirks
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v4] xhci: add traces for debug messages in xhci_address_device()
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: [RFC 1/4] xhci: add trace for debug messages related to quirks
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: [RFC 1/4] xhci: add trace for debug messages related to quirks
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RFC 3/4] xhci: add xhci_address_ctx trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC 4/4] xhci: add xhci_cmd_completion trace event
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC 2/4] xhci: add trace for debug messages related to endpoint reset
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC 1/4] xhci: add trace for debug messages related to quirks
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• [RFC v2] xhci: add trace for debug messages related to changing contexts
  • From: Xenia Ragiadakou <burzalodowa@xxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Mark Wielaard <mjw@xxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Help adding trace events to xHCI
  • From: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx>
• Re: [URGENT] trace-cmd: Fix for all stable versions for up coming fix in Linux v3.10
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [URGENT] trace-cmd: Fix for all stable versions for up coming fix in Linux v3.10
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: pytimechart - first use feedback
  • From: "Turgis, Frederic" <f-turgis@xxxxxx>
• pytimechart - first use feedback
  • From: "Turgis, Frederic" <f-turgis@xxxxxx>
• pytimechart - first use feedback
  • From: "Turgis, Frederic" <f-turgis@xxxxxx>
• Re: userstacktrace entries coming out as all zeros
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• userstacktrace entries coming out as all zeros
  • From: greenrd@xxxxxxxxxxx
• Function_graph questions
  • From: greenrd@xxxxxxxxxxx
• Re: [pytimechart] new cpuidle tracepoint
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Vishwanath Sripathy <vishwanath.sripathy@xxxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Vincent Guittot <vincent.guittot@xxxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Vincent Guittot <vincent.guittot@xxxxxxxxxx>
• Re: [pytimechart] new cpuidle tracepoint
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• [pytimechart] new cpuidle tracepoint
  • From: Vincent Guittot <vincent.guittot@xxxxxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• RE: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: "Zhang, Rui" <rui.zhang@xxxxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• RE: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: "R, Durgadoss" <durgadoss.r@xxxxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Zhang Rui <rui.zhang@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
• Re: Perf ABI versioning
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Perf ABI versioning
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
• Re: Perf ABI versioning
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Perf ABI versioning
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: Perf ABI versioning
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Perf ABI versioning
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Perf ABI versioning
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: Perf ABI versioning
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: Perf ABI versioning
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Perf ABI versioning
  • From: Thomas Renninger <trenn@xxxxxxx>
• Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH trace-cmd] kvm: don't warn on new fields
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH trace-cmd] kvm: don't warn on new fields
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH] Don't spam trace report about missing fields
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH] Don't spam trace report about missing fields
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] Don't spam trace report about missing fields
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH trace-cmd 0/3] kvm plugin updates
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• [PATCH trace-cmd 3/3] kvm: display the new kvm_exit info1 and info2 fields, if available
  • From: Avi Kivity <avi@xxxxxxxxxx>
• [PATCH trace-cmd 1/3] kvm: parse svm exit reason
  • From: Avi Kivity <avi@xxxxxxxxxx>
• [PATCH trace-cmd 2/3] kvm: fix typo "UNKOWN"
  • From: Avi Kivity <avi@xxxxxxxxxx>
• [PATCH trace-cmd 0/3] kvm plugin updates
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: trace_printk() support in trace-cmd
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• trace_printk() support in trace-cmd
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH] trace-view: Handle unknown events more gracefully
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] trace-view: Handle unknown events more gracefully
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: [PATCH] Add RPM packaging to trace-cmd
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH] Add RPM packaging to trace-cmd
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH] Add RPM packaging to trace-cmd
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 4/4] PERF: fix power:cpu_idle double end events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 4/4] PERF: fix power:cpu_idle double end events
  • From: Robert Schöne <robert.schoene@xxxxxxxxxxxxx>
• [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [linux-pm] [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 3/3] PERF(userspace): Adjust perf timechart to the new power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 1/3] PERF: Do not export power_frequency, but power_start event
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 3/3] PERF(userspace): Adjust perf timechart to the new power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Cleanup and enhance power trace events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [RFC] PERF: fix power:cpu_idle double end events and missing acpi_idle events - make cpu_idle power events cpuidle sysfs conform
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 4/4] PERF: fix power:cpu_idle double end events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 2/4] PERF(kernel): Cleanup power events V3
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 3/4] PERF(userspace): Adjust perf timechart to the new power events V3
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 1/4] PERF: Do not export power_frequency, but power_start event
  • From: Thomas Renninger <trenn@xxxxxxx>
• Cleanup and fixes for power trace events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 4/4] PERF: fix power:cpu_idle double end events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-pm] [PATCH] PERF(kernel): Cleanup power events V2
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] PERF(kernel): Cleanup power events V2
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• [PATCH] PERF(userspace): Adjust perf timechart to the new power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH] PERF(kernel): Cleanup power events V2
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• [PATCH 2/3] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 1/3] PERF: Do not export power_frequency, but power_start event
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 3/3] PERF(userspace): Adjust perf timechart to the new power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Felix Jirka <felix.jirka@xxxxxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: Kernel freeze during ftrace startup test (x86)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Kernel freeze during ftrace startup test (x86)
  • From: Felix Jirka <felix.jirka@xxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] trace-cmd: Plug startup race between flush_threads and recorders
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] trace-cmd: Plug startup race between flush_threads and recorders
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• [PATCH] trace-view: Handle unknown events more gracefully
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: [PATCH] plugin_kvm: fix kvm_exit rip formatting
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] plugin_kvm: fix kvm_exit rip formatting
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH trace-cmd] plugin_kvm: remove stray line from kvm_emulate_insn_handler()
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Pierre Tardy <tardyp@xxxxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: PATCH [0/4] perf: clean-up of power events API
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 3/4] perf: add calls to suspend trace point
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 2/4] perf: add OMAP support for the new power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [linux-pm] [PATCH] tracing, perf: add more power related events
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 4/4] perf: provide a DEPRECTAED power trace API to user space
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH 4/4] perf: provide a DEPRECTAED power trace API to user space
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• [PATCH 4/4] perf: provide a DEPRECTAED power trace API to user space
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• [PATCH 3/4] perf: add calls to suspend trace point
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• [PATCH 2/4] perf: add OMAP support for the new power events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• [PATCH 1/4] perf: cleanup power events API
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• PATCH [0/4] perf: clean-up of power events API
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• [PATCH 1/2] PERF(kernel): Cleanup power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 2/2] PERF(userspace): Adjust perf timechart to the new power events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Perf: Power events/tracepoints cleanups
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• [PATCH trace-cmd] plugin_kvm: remove stray line from kvm_emulate_insn_handler()
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn
  • From: Avi Kivity <avi@xxxxxxxxxx>
• [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx>
• Re: [PATCH] tracing, perf: add more power related events
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: [PATCH] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Thomas Renninger <trenn@xxxxxxx>
• Re: [PATCH 2/2] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH 2/2] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Thomas Renninger <trenn@xxxxxxx>
• [RFC] Common Trace Format Requirements (v1.2)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/2] acpi-cpufreq: Fix CPU_ANY CPUFREQ_{PRE,POST}CHANGE notification
  • From: Venkatesh Pallipadi <venki@xxxxxxxxxx>
• [PATCH 2/2] x86 cpufreq: Make trace_power_frequency cpufreq driver independent
  • From: Thomas Renninger <trenn@xxxxxxx>
• [PATCH 1/2] acpi-cpufreq: Fix CPU_ANY CPUFREQ_{PRE,POST}CHANGE notification
  • From: Thomas Renninger <trenn@xxxxxxx>
• Implement trace_power_frequency for all cpufreq drivers
  • From: Thomas Renninger <trenn@xxxxxxx>
• switch to public mailing list archives ?
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>