Re: [Patch] tracing: tell mm_migrate_pages event about numa_misplaced

From: Steven Rostedt
Date: Mon Jun 23 2014 - 10:31:20 EST


On Mon, 23 Jun 2014 15:21:59 +0100
Mel Gorman <mgorman@xxxxxxx> wrote:

> On Fri, Jun 20, 2014 at 11:49:16AM -0700, Max Asbock wrote:
> >
> > The mm_migrate_pages trace event reports a reason for the migration, typically as a
> > symbolic string. The exception is the reason MR_NUMA_MISPLACED for which it just displays
> > the numeric value:
> > mm_migrate_pages: nr_succeeded=1 nr_failed=0 mode=MIGRATE_ASYNC reason=0x5
> >
> > This patch makes the output consistent by introducing a string value for MR_NUMA_MISPLACED.
> > The event is then reported as:
> > mm_migrate_pages: nr_succeeded=1 nr_failed=0 mode=MIGRATE_ASYNC reason=numa_misplaced
> >
> > Signed-off-by: Max Asbock <masbock@xxxxxxxxxxxxxxxxxx>
>
> Acked-by: Mel Gorman <mgorman@xxxxxxx>
>

Would you like to take this? Or Andrew?

You can add my Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx>


-- Steve
--
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/