From: Steven Rostedt <rostedt@goodmis.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH 2/3] mm, compaction: export tracepoints zone names to userspace
Date: Mon, 31 Aug 2015 11:13:04 -0400 [thread overview]
Message-ID: <20150831111304.3888a8f6@gandalf.local.home> (raw)
In-Reply-To: <55E46C8E.8070906@suse.cz>
On Mon, 31 Aug 2015 17:02:38 +0200
Vlastimil Babka <vbabka@suse.cz> wrote:
> >> +#define ZONE_TYPE \
> >> + IFDEF_ZONE_DMA( EM (ZONE_DMA, "DMA")) \
> >> + IFDEF_ZONE_DMA32( EM (ZONE_DMA32, "DMA32")) \
> >> + EM (ZONE_NORMAL, "Normal") \
> >> + IFDEF_ZONE_HIGHMEM( EM (ZONE_HIGHMEM,"HighMem")) \
> >> + EMe(ZONE_MOVABLE,"Movable")
> >> +
> >
> > Hmm, have you tried to compile this with CONFIG_ZONE_HIGHMEM disabled,
> > and CONFIG_ZONE_DMA and/or CONFIG_ZONE_DMA32 enabled?
>
> Yep, that's standard x86_64 situation (highmem disabled, dma+dma32 enabled).
>
> > The EMe() macro must come last, as it doesn't have the ending comma and
> > the __print_symbolic() can fail to compile due to it.
>
> Thanks to ZONE_MOVABLE being unconditional, EMe(ZONE_MOVABLE...) is
> always last. Otherwise the macros would get even more ugly...
Ah! My mistake was to see where the end parenthesis of
IFDEF_ZONE_HIGHMEM() laid. It looked to me that it encompassed
ZONE_MOVABLE. But obviously it does not.
-- Steve
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-08-31 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:24 [PATCH 1/3] mm, compaction: export tracepoints status strings " Vlastimil Babka
2015-08-27 15:24 ` [PATCH 2/3] mm, compaction: export tracepoints zone names " Vlastimil Babka
2015-08-31 14:58 ` Steven Rostedt
2015-08-31 15:02 ` Vlastimil Babka
2015-08-31 15:13 ` Steven Rostedt [this message]
2015-08-31 15:32 ` Steven Rostedt
2015-08-27 15:24 ` [PATCH 3/3] mm, compaction: disginguish contended status in tracepoint Vlastimil Babka
2015-09-07 5:53 ` Joonsoo Kim
2015-09-08 16:29 ` Vlastimil Babka
2015-08-31 14:55 ` [PATCH 1/3] mm, compaction: export tracepoints status strings to userspace Steven Rostedt
2015-08-31 15:27 ` Vlastimil Babka
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=20150831111304.3888a8f6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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