From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mel@csn.ul.ie>,
Christoph Hellwig <hch@infradead.org>,
Rik van Riel <riel@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Frederic Weisbecker <fweisbec@gmail.com>,
Theodore Tso <tytso@mit.edu>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Zhaolei <zhaolei@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jason Baron <jbaron@redhat.com>,
Jiaying Zhang <jiayingz@google.com>
Subject: Re: [RFC PATCH 5/5] tracing/events: modify kmem print to new format
Date: Tue, 09 Jun 2009 09:12:42 +0200 [thread overview]
Message-ID: <1244531562.13761.9955.camel@twins> (raw)
In-Reply-To: <20090609014747.188279837@goodmis.org>
On Mon, 2009-06-08 at 21:45 -0400, Steven Rostedt wrote:
> +#define show_gfp_flags(end...) \
> + "0=GFP_NOWAIT," \
> + "0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s," \
> + "0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s," \
> + "0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s,0x%lx=%s," \
> + "0x%lx=%s,0x%lx=%s>" end , \
> + (unsigned long)GFP_HIGHUSER_MOVABLE, "GFP_HIGHUSER_MOVABLE", \
> + (unsigned long)GFP_HIGHUSER, "GFP_HIGHUSER", \
> + (unsigned long)GFP_USER, "GFP_USER", \
> + (unsigned long)GFP_TEMPORARY, "GFP_TEMPORARY", \
> + (unsigned long)GFP_KERNEL, "GFP_KERNEL", \
> + (unsigned long)GFP_NOFS, "GFP_NOFS", \
> + (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"
Just curious, how unhappy does stuff become when we add a __GFP_ flag
and forget to extend this table?
next prev parent reply other threads:[~2009-06-09 7:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 1:45 [RFC PATCH 0/5] simplify the print fmt in the event format files Steven Rostedt
2009-06-09 1:45 ` [RFC PATCH 1/5] tracing: add trace_seq_vprint interface Steven Rostedt
2009-06-09 1:45 ` [RFC PATCH 2/5] tracing/events: nicer print format for parsing Steven Rostedt
2009-06-09 19:22 ` Frederic Weisbecker
2009-06-09 19:45 ` Steven Rostedt
2009-06-09 20:01 ` Mathieu Desnoyers
2009-06-10 1:59 ` Lai Jiangshan
2009-06-10 5:37 ` Steven Rostedt
2009-06-10 9:37 ` Christoph Hellwig
2009-06-10 9:48 ` Christoph Hellwig
2009-06-10 10:11 ` Ingo Molnar
2009-06-10 11:31 ` Frédéric Weisbecker
2009-06-10 11:51 ` Frédéric Weisbecker
2009-06-10 12:18 ` Steven Rostedt
2009-06-10 17:16 ` Ingo Molnar
2009-06-10 17:56 ` Steven Rostedt
2009-06-10 18:39 ` [PATCH][GIT PULL] tracing: do not translate event helper macros in print format Steven Rostedt
2009-06-10 20:48 ` Ingo Molnar
2009-06-11 12:52 ` Christoph Hellwig
2009-06-11 13:04 ` Steven Rostedt
2009-06-10 14:32 ` [RFC PATCH 2/5] tracing/events: nicer print format for parsing Mathieu Desnoyers
2009-06-10 12:47 ` Steven Rostedt
2009-06-09 1:45 ` [RFC PATCH 3/5] tracing/events: modify irq print to new format Steven Rostedt
2009-06-10 9:42 ` Christoph Hellwig
2009-06-10 12:23 ` Steven Rostedt
2009-06-09 1:45 ` [RFC PATCH 4/5] tracing/events: modify sched " Steven Rostedt
2009-06-09 1:45 ` [RFC PATCH 5/5] tracing/events: modify kmem " Steven Rostedt
2009-06-09 7:12 ` Peter Zijlstra [this message]
2009-06-09 8:06 ` Mel Gorman
2009-06-09 13:08 ` Steven Rostedt
2009-06-09 12:07 ` [RFC PATCH 0/5] simplify the print fmt in the event format files Ingo Molnar
2009-06-09 12:57 ` 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=1244531562.13761.9955.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--cc=zhaolei@cn.fujitsu.com \
/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