| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
1. Real-time CPUs are loaded at startup
2. A menu item for loading all real-time tasks is added
3. Black boxes appear around run times when zoomed in
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Each plot processes only the records which fit within the time window displayed.
When passing records into a real-time plot, kernelshark will now decide if a
record is within the current time window using real-time timestamps, instead of
the old ftrace timestamps.
This change also enables infinite zooming into the real-time plots.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Logic is added to extract current job / release / deadline from a time.
Hovering over a location in an real-time task plot will show this.
|
|
|
|
|
| |
When you hover close enough to an events time, the event name will
display. This time is based on _litmus_ time, not record time.
|
|
|
|
|
| |
Vertical lines mark events which were run either with the tasks pid
or ran on the task's cpu while it is executing.
|
| |
|
|
|
|
| |
Currently they copy the functionality of regular task.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The __print_symbolic() function takes a sequence of key-value pairs for
pretty-printing a constant. The new kvm:kvm_exit print fmt uses the
expression:
__print_symbolic(..., { 0x040 + 1, "DB excp" }, ...)
Currently only atoms are supported and this print fmt fails to parse.
This patch adds support for expressions instead of just atoms so that
0x040 + 1 is parsed successfully.
Link: http://lkml.kernel.org/r/1315131959-7452-1-git-send-email-stefanha@linux.vnet.ibm.com
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Avi Kivity <avi@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Padding events store size in bytes, not words. Usually this ends up pushing
the parser off the current page, but occasionally not, and when not,
it ends up desynchronizing the parser from the event stream. This would
manifest as a lot of "ug!" messages from trace-cmd, and kernelshark
crashing before displaying the UI.
Link: http://lkml.kernel.org/r/1327633215-4013-1-git-send-email-dhsharp@google.com
Signed-off-by: David Sharp <dhsharp@google.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The BLK_TC_BARRIER flag was dropped in Linux commit c09c47caedc in
August 2011. The blk plugin fails to build against recent kernel
headers. Since no flag bits were left, the new BLK_TC_FLUSH flag reused
the BLK_TC_BARRIER bit. The new BLK_TC_FUA flag was also added.
This patch updates fill_rwbs() to reflect the new
BLK_TC_FLUSH/BLK_TC_FUA flags. This allows plugin_blk.c to build
successfully on recent kernels. Most of the patch deals with detecting
old vs new kernel headers so we can build successfully on both.
(Namhyung Kim recommended using the makefile check used by perf and
other tools)
Link: http://lkml.kernel.org/r/1326108639-13904-1-git-send-email-stefanha@linux.vnet.ibm.com
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When %pM is used, the arg value must be a 6 byte character that
will be printed as a 6 byte MAC address. But the code does a break
over the main code which updates the current processing arg to point
to the next arg. If there are other print arguments after a %pM,
they will be off by one. The next arg will still be processing the
%pM arg.
Reported-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Add ability for the Makefile to respect LDFLAGS.
Also remove hardcoded /usr/local/include include path.
Link: http://lkml.kernel.org/r/4ED6C808.9030003@linux.intel.com
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
| |
The RT kernel added a migrate disable counter in all events. Add support
to show this in the latency format.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
| |
The arg notation of '*' in bprintks is not handled by the parser.
Implement it so that they show up properly in the output and do not
kill the tracer from reporting events.
Reported-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
| |
As a pointer can be converted into a function name, let the filters
work with the function name as well as with the pointer number.
If the comparison expects a string, then convert numbers into functions,
but only when the number is the same size as a long.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
| |
Fix memset(ptr, 0, sizeof(ptr)) to memset(ptr, 0, sizeof(*ptr));
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
| |
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
| |
I have been informed that documentation (man pages) should be installed
by default and not just separate.
Reported-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
A update is made to the sched:sched_switch event that adds some
logic to the first parameter of the __print_flags() that shows the
state of tasks. This change cause trace-cmd to fail parsing the flags.
A simple fix is needed to have the parser be able to process ops
within the argument.
Reported-by: Andrew Vagin <avagin@openvz.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
| |
Replace keywords "private" and "bool" from parse-events.h to allow
it to be used in C++ programs.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
| |
Add multiply and divide operations in the printk format.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
| |
If -a is set with trace-cmd extract, simply ignore it,
otherwise, all events will be recorded twice. Once at this location,
and once during extracting.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the trace-cmd extract function uses the forked threads to
read the data from the ring buffers. As this is not a live trace and
the program does not end till all the buffers are flushed to disk,
there is no need to use the threads. Just serially read each buffer
into a file and then pull them together normally.
This also fixes a bug that was triggered in the kernel where reading
the trace_pipe_raw file after EOF will yield the last page again,
causing the trace-cmd extract to produce duplicate pages.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|
|
|
|
|
|
|
|
|
| |
When the main thread tells the recorders that they are finished,
have the recorders still use splice till all data is read that
splice can handle (full page sizes only). Then use the read function
for the rest.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
|