[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 2 Feb 2016 14:21:57 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: David Rientjes <rientjes@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-arch@...r.kernel.org,
linux-s390@...r.kernel.org, x86@...nel.org,
linuxppc-dev@...ts.ozlabs.org, davem@...emloft.net,
Joonsoo Kim <iamjoonsoo.kim@....com>, davej@...emonkey.org.uk
Subject: Re: [PATCH v3 2/3] x86: query dynamic DEBUG_PAGEALLOC setting
On Tue, 2 Feb 2016 22:53:36 +0100 Christian Borntraeger <borntraeger@...ibm.com> wrote:
> >> I don't think we should have a CONFIG_DEBUG_PAGEALLOC that does some stuff
> >> and then a commandline parameter or CONFIG_DEBUG_PAGEALLOC_ENABLE_DEFAULT
> >> to enable more stuff. It should either be all enabled by the commandline
> >> (or config option) or split into a separate entity.
> >> CONFIG_DEBUG_PAGEALLOC_LIGHT and CONFIG_DEBUG_PAGEALLOC would be fine, but
> >> the current state is very confusing about what is being done and what
> >> isn't.
> >>
> >
> > Ping?
> >
> https://lkml.org/lkml/2016/1/29/266
That's already in linux-next so I can't apply it.
Well, I can, but it's a hassle. What's happening here?
Powered by blists - more mailing lists