From: Sebastian Siewior <bigeasy@linutronix.de>
To: Ingo Molnar <mingo@redhat.com>
Cc: Greg Ungerer <gerg@uclinux.org>,
uclinux-dev@uclinux.org, linux-kernel@vger.kernel.org,
Sebastian Siewior <bigeasy@linutronix.de>
Subject: [PATCH] ftrace: also dump the entry->flag field
Date: Tue, 13 May 2008 18:52:45 +0200 [thread overview]
Message-ID: <1210697565-3106-4-git-send-email-bigeasy@linutronix.de> (raw)
In-Reply-To: <1210697565-3106-1-git-send-email-bigeasy@linutronix.de>
The data is collected anyway so why not print it?
Signed-off-by: Sebastian Siewior <bigeasy@linutronix.de>
---
kernel/trace/trace.c | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 06c85b3..0b0e996 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1514,7 +1514,14 @@ static int print_trace_fmt(struct trace_iterator *iter)
ret = trace_seq_printf(s, "[%02d] ", iter->cpu);
if (!ret)
return 0;
- ret = trace_seq_printf(s, "%5lu.%06lu: ", secs, usec_rem);
+ ret = trace_seq_printf(s, "%5lu.%06lu ", secs, usec_rem);
+ if (!ret)
+ return 0;
+ ret = trace_seq_printf(s, "{%2u|%c%c%c%c}: ", entry->preempt_count,
+ entry->flags & TRACE_FLAG_IRQS_OFF ? '.' : 'I',
+ entry->flags & TRACE_FLAG_NEED_RESCHED ? 'R' : '.',
+ entry->flags & TRACE_FLAG_HARDIRQ ? 'H' : '.',
+ entry->flags & TRACE_FLAG_SOFTIRQ ? 'S' : '.');
if (!ret)
return 0;
--
1.5.4.3
next prev parent reply other threads:[~2008-05-13 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 16:52 [RFC / PATCH] ftrace support on m68knommu Sebastian Siewior
2008-05-13 16:52 ` [PATCH] m68knommu: add FTRACE support Sebastian Siewior
2008-05-16 13:02 ` Steven Rostedt
2008-05-13 16:52 ` [PATCH] m68knommu: add read_barrier_depends() and irqs_disabled_flags() Sebastian Siewior
2008-05-13 16:52 ` Sebastian Siewior [this message]
2008-05-16 12:59 ` [RFC / PATCH] ftrace support on m68knommu Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1210697565-3106-4-git-send-email-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=uclinux-dev@uclinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).