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 <masb...@linux.vnet.ibm.com>
migrate.h | 1 +
1 file changed, 1 insertion(+)
--- linux-3.16-rc1/include/trace/events/migrate.h.orig 2014-06-20
10:00:26.768410407 -0700
+++ linux-3.16-rc1/include/trace/events/migrate.h 2014-06-20
10:01:55.432410334 -0700
@@ -17,6 +17,7 @@
{MR_MEMORY_HOTPLUG, "memory_hotplug"}, \
{MR_SYSCALL, "syscall_or_cpuset"}, \
{MR_MEMPOLICY_MBIND, "mempolicy_mbind"}, \
+ {MR_NUMA_MISPLACED, "numa_misplaced"}, \
{MR_CMA, "cma"}
TRACE_EVENT(mm_migrate_pages,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
