From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 3/3] tracing: add flag output for kmem events
Date: Fri, 15 May 2009 23:23:29 +0200 [thread overview]
Message-ID: <20090515212328.GA6156@nowhere> (raw)
In-Reply-To: <20090515210718.211132919@goodmis.org>
On Fri, May 15, 2009 at 05:03:45PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@redhat.com>
>
> This patch changes the output for gfp_flags from being a simple hex value
> to the actual names.
>
> gfp_flags=GFP_ATOMIC instead of gfp_flags=00000020
>
> And even
>
> gfp_flags=GFP_KERNEL instead of gfp_flags=000000d0
>
> [ Impact: more human readable output from tracer ]
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Nice!
> ---
> include/trace/events/kmem.h | 43 +++++++++++++++++++++++++++++++++++--------
> 1 files changed, 35 insertions(+), 8 deletions(-)
>
> diff --git a/include/trace/events/kmem.h b/include/trace/events/kmem.h
> index c22c42f..9b3886b 100644
> --- a/include/trace/events/kmem.h
> +++ b/include/trace/events/kmem.h
> @@ -7,6 +7,33 @@
> #undef TRACE_SYSTEM
> #define TRACE_SYSTEM kmem
>
> +#define show_gfp_flags(flags) \
> + (flags) ? __print_flags(flags, "|", \
> + (unsigned long)GFP_KERNEL, "GFP_KERNEL", \
> + (unsigned long)GFP_NOFS, "GFP_NOFS", \
> + (unsigned long)GFP_TEMPORARY, "GFP_TEMPORARY", \
> + (unsigned long)GFP_USER, "GFP_USER", \
Because you clear the mask value after finding out a matching mask
string, you should sort the masks from the highest number of bits
to the lowest.
GFP_USER should be placed before GFP_KERNEL otherwise it will always be
eaten.
Instead of GFP_USER, you will get:
GFP_KERNEL | __GFP_HARDWALL
> + (unsigned long)GFP_HIGHUSER, "GFP_HIGHUSER", \
Ditto, it should be placed before GFP_USER otherwise you will get:
GFP_USER | __GFP_HIGHMEM
> + (unsigned long)GFP_HIGHUSER_MOVABLE, "GFP_HIGHUSER_MOVABLE", \
And this one before HIGH_USER otherwise:
GFP_HIGHUSER__GFP_MOVABLE
:-)
Frederic.
> + (unsigned long)GFP_ATOMIC, "GFP_ATOMIC", \
> + (unsigned long)GFP_NOIO, "GFP_NOIO", \
> + (unsigned long)__GFP_HIGH, "GFP_HIGH", \
> + (unsigned long)__GFP_WAIT, "GFP_WAIT", \
> + (unsigned long)__GFP_IO, "GFP_IO", \
> + (unsigned long)__GFP_COLD, "GFP_COLD", \
> + (unsigned long)__GFP_NOWARN, "GFP_NOWARN", \
> + (unsigned long)__GFP_REPEAT, "GFP_REPEAT", \
> + (unsigned long)__GFP_NOFAIL, "GFP_NOFAIL", \
> + (unsigned long)__GFP_NORETRY, "GFP_NORETRY", \
> + (unsigned long)__GFP_COMP, "GFP_COMP", \
> + (unsigned long)__GFP_ZERO, "GFP_ZERO", \
> + (unsigned long)__GFP_NOMEMALLOC, "GFP_NOMEMALLOC", \
> + (unsigned long)__GFP_HARDWALL, "GFP_HARDWALL", \
> + (unsigned long)__GFP_THISNODE, "GFP_THISNODE", \
> + (unsigned long)__GFP_RECLAIMABLE, "GFP_RECLAIMABLE", \
> + (unsigned long)__GFP_MOVABLE, "GFP_MOVABLE" \
> + ) : "GFP_NOWAIT"
> +
> TRACE_EVENT(kmalloc,
>
> TP_PROTO(unsigned long call_site,
> @@ -33,12 +60,12 @@ TRACE_EVENT(kmalloc,
> __entry->gfp_flags = gfp_flags;
> ),
>
> - TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%08x",
> + TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s",
> __entry->call_site,
> __entry->ptr,
> __entry->bytes_req,
> __entry->bytes_alloc,
> - __entry->gfp_flags)
> + show_gfp_flags(__entry->gfp_flags))
> );
>
> TRACE_EVENT(kmem_cache_alloc,
> @@ -67,12 +94,12 @@ TRACE_EVENT(kmem_cache_alloc,
> __entry->gfp_flags = gfp_flags;
> ),
>
> - TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%08x",
> + TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s",
> __entry->call_site,
> __entry->ptr,
> __entry->bytes_req,
> __entry->bytes_alloc,
> - __entry->gfp_flags)
> + show_gfp_flags(__entry->gfp_flags))
> );
>
> TRACE_EVENT(kmalloc_node,
> @@ -104,12 +131,12 @@ TRACE_EVENT(kmalloc_node,
> __entry->node = node;
> ),
>
> - TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%08x node=%d",
> + TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s node=%d",
> __entry->call_site,
> __entry->ptr,
> __entry->bytes_req,
> __entry->bytes_alloc,
> - __entry->gfp_flags,
> + show_gfp_flags(__entry->gfp_flags),
> __entry->node)
> );
>
> @@ -142,12 +169,12 @@ TRACE_EVENT(kmem_cache_alloc_node,
> __entry->node = node;
> ),
>
> - TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%08x node=%d",
> + TP_printk("call_site=%lx ptr=%p bytes_req=%zu bytes_alloc=%zu gfp_flags=%s node=%d",
> __entry->call_site,
> __entry->ptr,
> __entry->bytes_req,
> __entry->bytes_alloc,
> - __entry->gfp_flags,
> + show_gfp_flags(__entry->gfp_flags),
> __entry->node)
> );
>
> --
> 1.6.2.4
>
> --
next prev parent reply other threads:[~2009-05-15 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:03 [PATCH 0/3] tracing/events: enumerating flags Steven Rostedt
2009-05-15 21:03 ` [PATCH 1/3] tracing: add __print_flags for events Steven Rostedt
2009-05-18 17:38 ` Christoph Hellwig
2009-05-20 22:13 ` Steven Rostedt
2009-05-20 22:59 ` Christoph Hellwig
2009-05-20 23:02 ` Steven Rostedt
2009-05-20 23:04 ` Christoph Hellwig
2009-05-21 1:10 ` KOSAKI Motohiro
2009-05-15 21:03 ` [PATCH 2/3] tracing: add previous task state info to sched switch event Steven Rostedt
2009-05-15 21:03 ` [PATCH 3/3] tracing: add flag output for kmem events Steven Rostedt
2009-05-15 21:23 ` Frederic Weisbecker [this message]
2009-05-15 21:50 ` Steven Rostedt
2009-05-15 23:40 ` Eduard - Gabriel Munteanu
2009-05-15 23:52 ` 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=20090515212328.GA6156@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.