mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Asbock <masbock@linux.vnet.ibm.com>
To: rostedt@goodmis.org, mingo@redhat.com, mgorman@suse.de,
	akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [Patch] tracing: tell mm_migrate_pages event about numa_misplaced
Date: Fri, 20 Jun 2014 11:49:16 -0700	[thread overview]
Message-ID: <1403290156.4484.10.camel@oc3432500282.ibm.com> (raw)


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@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,



             reply	other threads:[~2014-06-20 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 18:49 Max Asbock [this message]
2014-06-23 14:21 ` Mel Gorman
2014-06-23 14:31   ` Steven Rostedt
2014-06-23 14:56     ` Mel Gorman

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=1403290156.4484.10.camel@oc3432500282.ibm.com \
    --to=masbock@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®