From: Li Zefan <lizf@cn.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kmemtrace: print binary output only if 'bin' option is set
Date: Fri, 03 Jul 2009 08:36:42 +0800 [thread overview]
Message-ID: <4A4D529A.3090706@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907020854440.9647@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Thu, 2 Jul 2009, Li Zefan wrote:
>> ---
>> kernel/trace/kmemtrace.c | 119 ++++++++++++++++++++++++++++++++++------------
>> 1 files changed, 89 insertions(+), 30 deletions(-)
>>
>> diff --git a/kernel/trace/kmemtrace.c b/kernel/trace/kmemtrace.c
>> index 1edaa95..9a58f37 100644
>> --- a/kernel/trace/kmemtrace.c
>> +++ b/kernel/trace/kmemtrace.c
>> @@ -239,12 +239,51 @@ struct kmemtrace_user_event_alloc {
>> };
>>
>> static enum print_line_t
>> -kmemtrace_print_alloc_user(struct trace_iterator *iter,
>> - struct kmemtrace_alloc_entry *entry)
>> +kmemtrace_print_alloc_user(struct trace_iterator *iter, int flags)
>> +{
>> + struct trace_seq *s = &iter->seq;
>> + struct kmemtrace_alloc_entry *entry;
>> + int ret;
>> +
>> + trace_assign_type(entry, iter->ent);
>> +
>> + ret = trace_seq_printf(s, "type_id %d call_site %lu ptr %lu "
>> + "bytes_req %lu bytes_alloc %lu gfp_flags %lu node %d\n",
>> + entry->type_id, entry->call_site, (unsigned long)entry->ptr,
>> + (unsigned long)entry->bytes_req, (unsigned long)entry->bytes_alloc,
>> + (unsigned long)entry->gfp_flags, entry->node);
>
> Could we make the call_site %pF ? That way we can see the name of the
> function and not just the address.
>
Sure, I'll fix it. I just restored the old format.
prev parent reply other threads:[~2009-07-03 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 6:12 [PATCH] kmemtrace: print binary output only if 'bin' option is set Li Zefan
2009-07-02 6:31 ` Pekka Enberg
2009-07-02 6:42 ` Eduard - Gabriel Munteanu
2009-07-02 12:55 ` Steven Rostedt
2009-07-03 0:36 ` Li Zefan [this message]
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=4A4D529A.3090706@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.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