linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, Joonsoo Kim <js1304@gmail.com>,
	Yang Shi <yang.shi@linaro.org>, Mel Gorman <mgorman@suse.de>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: disallow early_pfn_to_nid on configurations which do not implement it
Date: Thu, 6 Jul 2017 08:50:56 +0200	[thread overview]
Message-ID: <20170706065055.GB29724@dhcp22.suse.cz> (raw)
In-Reply-To: <20170705160055.013fa5ff34bdf1f6efa4e6ce@linux-foundation.org>

On Wed 05-07-17 16:00:55, Andrew Morton wrote:
> On Tue,  4 Jul 2017 09:58:03 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> 
> > From: Michal Hocko <mhocko@suse.com>
> > 
> > early_pfn_to_nid will return node 0 if both HAVE_ARCH_EARLY_PFN_TO_NID
> > and HAVE_MEMBLOCK_NODE_MAP are disabled. It seems we are safe now
> > because all architectures which support NUMA define one of them (with an
> > exception of alpha which however has CONFIG_NUMA marked as broken) so
> > this works as expected. It can get silently and subtly broken too
> > easily, though. Make sure we fail the compilation if NUMA is enabled and
> > there is no proper implementation for this function. If that ever
> > happens we know that either the specific configuration is invalid
> > and the fix should either disable NUMA or enable one of the above
> > configs.
> > 
> > ...
> >
> > --- a/include/linux/mmzone.h
> > +++ b/include/linux/mmzone.h
> > @@ -1055,6 +1055,7 @@ static inline struct zoneref *first_zones_zonelist(struct zonelist *zonelist,
> >  	!defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP)
> >  static inline unsigned long early_pfn_to_nid(unsigned long pfn)
> >  {
> > +	BUILD_BUG_ON(IS_ENABLED(CONFIG_NUMA));
> >  	return 0;
> >  }
> >  #endif
> 
> Wouldn't this be more conventional?

Well, both would lead to a compilation errors which is what I want to
achieve. The above is easier to parse IMHO. If you believe a longer
ifdef chain is better I won't object.

> --- a/include/linux/mmzone.h~a
> +++ a/include/linux/mmzone.h
> @@ -1052,7 +1052,8 @@ static inline struct zoneref *first_zone
>  #endif
>  
>  #if !defined(CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID) && \
> -	!defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP)
> +	!defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP) && \
> +	!defined(CONFIG_NUMA)
>  static inline unsigned long early_pfn_to_nid(unsigned long pfn)
>  {
>  	return 0;
> _
> 

-- 
Michal Hocko
SUSE Labs

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

      reply	other threads:[~2017-07-06  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  7:58 Michal Hocko
2017-07-04  9:28 ` Vlastimil Babka
2017-07-05 23:00 ` Andrew Morton
2017-07-06  6:50   ` Michal Hocko [this message]

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=20170706065055.GB29724@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=vbabka@suse.cz \
    --cc=yang.shi@linaro.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