From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
x86@kernel.org, linuxppc-dev@lists.ozlabs.org,
davem@davemloft.net, Joonsoo Kim <iamjoonsoo.kim@lge.com>,
davej@codemonkey.org.uk
Subject: Re: [PATCH v3 2/3] x86: query dynamic DEBUG_PAGEALLOC setting
Date: Tue, 2 Feb 2016 23:37:50 +0100 [thread overview]
Message-ID: <56B12FBE.3070909@de.ibm.com> (raw)
In-Reply-To: <20160202142157.1bfc6f81807faaa026957917@linux-foundation.org>
On 02/02/2016 11:21 PM, Andrew Morton wrote:
> On Tue, 2 Feb 2016 22:53:36 +0100 Christian Borntraeger <borntraeger@de.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?
I pushed it on my tree for kbuild testing purposes some days ago.
Will drop so that it can go via mm.
next prev parent reply other threads:[~2016-02-02 22:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 10:09 [PATCH v3 0/3] Optimize CONFIG_DEBUG_PAGEALLOC Christian Borntraeger
2016-01-27 10:09 ` Christian Borntraeger
2016-01-27 10:09 ` [PATCH v3 1/3] mm: provide debug_pagealloc_enabled() without CONFIG_DEBUG_PAGEALLOC Christian Borntraeger
2016-01-27 10:09 ` Christian Borntraeger
2016-01-27 10:10 ` [PATCH v3 2/3] x86: query dynamic DEBUG_PAGEALLOC setting Christian Borntraeger
2016-01-27 10:10 ` Christian Borntraeger
2016-01-27 22:17 ` David Rientjes
2016-01-27 22:17 ` David Rientjes
2016-01-28 9:48 ` Christian Borntraeger
2016-01-28 9:48 ` Christian Borntraeger
2016-01-28 23:03 ` David Rientjes
2016-02-02 21:51 ` David Rientjes
2016-02-02 21:51 ` David Rientjes
2016-02-02 21:53 ` Christian Borntraeger
2016-02-02 21:53 ` Christian Borntraeger
2016-02-02 22:21 ` Andrew Morton
2016-02-02 22:37 ` Christian Borntraeger [this message]
2016-02-02 23:04 ` Andrew Morton
2016-02-03 0:13 ` Stephen Rothwell
2016-02-02 21:52 ` (unknown) David Rientjes via Linuxppc-dev
2016-01-28 23:04 ` (unknown) David Rientjes via Linuxppc-dev
2016-01-27 22:18 ` (unknown) David Rientjes via Linuxppc-dev
2016-01-27 10:10 ` [PATCH v3 3/3] s390: query dynamic DEBUG_PAGEALLOC setting Christian Borntraeger
2016-01-27 10:10 ` Christian Borntraeger
2016-01-27 22:18 ` David Rientjes
2016-01-27 22:18 ` David Rientjes
2016-01-27 22:22 ` (unknown) David Rientjes via Linuxppc-dev
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=56B12FBE.3070909@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rientjes@google.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).