Re: [PATCH 3/3] tracing: add flag output for kmem events

From: Eduard - Gabriel Munteanu
Date: Fri May 15 2009 - 19:40:23 EST


On Fri, May 15, 2009 at 05:03:45PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <srostedt@xxxxxxxxxx>
>
> 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@xxxxxxxxxxx>
> ---
> include/trace/events/kmem.h | 43 +++++++++++++++++++++++++++++++++++--------
> 1 files changed, 35 insertions(+), 8 deletions(-)

As long as it doesn't touch (and I see it doesn't) the raw kmemtrace
output for kmemtrace-user, I'm okay with this sort of changes.

Acked-by: Eduard - Gabriel Munteanu <eduard.munteanu@xxxxxxxxxxx>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/