From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: David Rientjes <rientjes@google.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH/RFC 3/3] s390: query dynamic DEBUG_PAGEALLOC setting
Date: Wed, 27 Jan 2016 09:19:18 +0900 [thread overview]
Message-ID: <20160127001918.GA7089@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <alpine.DEB.2.10.1601261525580.25141@chino.kir.corp.google.com>
On Tue, Jan 26, 2016 at 03:29:38PM -0800, David Rientjes wrote:
> On Tue, 26 Jan 2016, Heiko Carstens wrote:
>
> > On Tue, Jan 26, 2016 at 10:18:25AM +0100, Christian Borntraeger wrote:
> > > We can use debug_pagealloc_enabled() to check if we can map
> > > the identity mapping with 1MB/2GB pages as well as to print
> > > the current setting in dump_stack.
> > >
> > > Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> > > ---
> > > arch/s390/kernel/dumpstack.c | 4 +++-
> > > arch/s390/mm/vmem.c | 10 ++++------
> > > 2 files changed, 7 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/arch/s390/kernel/dumpstack.c b/arch/s390/kernel/dumpstack.c
> > > index dc8e204..a1c0530 100644
> > > --- a/arch/s390/kernel/dumpstack.c
> > > +++ b/arch/s390/kernel/dumpstack.c
> > > @@ -11,6 +11,7 @@
> > > #include <linux/export.h>
> > > #include <linux/kdebug.h>
> > > #include <linux/ptrace.h>
> > > +#include <linux/mm.h>
> > > #include <linux/module.h>
> > > #include <linux/sched.h>
> > > #include <asm/processor.h>
> > > @@ -186,7 +187,8 @@ void die(struct pt_regs *regs, const char *str)
> > > printk("SMP ");
> > > #endif
> > > #ifdef CONFIG_DEBUG_PAGEALLOC
> > > - printk("DEBUG_PAGEALLOC");
> > > + printk("DEBUG_PAGEALLOC(%s)",
> > > + debug_pagealloc_enabled() ? "enabled" : "disabled");
> > > #endif
> >
> > I'd prefer if you change this to
> >
> > if (debug_pagealloc_enabled())
> > printk("DEBUG_PAGEALLOC");
> >
> > That way we can get rid of yet another ifdef. Having
> > "DEBUG_PAGEALLOC(disabled)" doesn't seem to be very helpful.
> >
>
> I'd agree if CONFIG_DEBUG_PAGEALLOC only did anything when
> debug_pagealloc_enabled() is true, but that doesn't seem to be the case.
> When CONFIG_DEBUG_SLAB is enabled, for instance, CONFIG_DEBUG_PAGEALLOC
> also enables stackinfo storing and poisoning and it's not guarded by
> debug_pagealloc_enabled().
>
> It seems like CONFIG_DEBUG_PAGEALLOC enables debugging functionality
> outside the scope of the debug_pagealloc=on kernel parameter, so
> DEBUG_PAGEALLOC(disabled) actually does mean something.
Hello, David.
I tried to fix CONFIG_DEBUG_SLAB case on 04/16 of following patchset.
http://thread.gmane.org/gmane.linux.kernel.mm/144527
I found that there are more sites to fix but not so many.
We can do it.
Thanks.
next prev parent reply other threads:[~2016-01-27 0:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 9:18 [PATCH/RFC 0/3] Optimize CONFIG_DEBUG_PAGEALLOC Christian Borntraeger
2016-01-26 9:18 ` Christian Borntraeger
2016-01-26 9:18 ` [PATCH/RFC 1/3] mm: provide debug_pagealloc_enabled() without CONFIG_DEBUG_PAGEALLOC Christian Borntraeger
2016-01-26 9:18 ` Christian Borntraeger
2016-01-26 23:23 ` David Rientjes
2016-01-26 9:18 ` [PATCH/RFC 2/3] x86: query dynamic DEBUG_PAGEALLOC setting Christian Borntraeger
2016-01-26 9:18 ` Christian Borntraeger
2016-01-26 9:18 ` [PATCH/RFC 3/3] s390: " Christian Borntraeger
2016-01-26 9:18 ` Christian Borntraeger
2016-01-26 18:19 ` Heiko Carstens
2016-01-26 18:19 ` Heiko Carstens
2016-01-26 20:38 ` Thomas Gleixner
2016-01-26 20:38 ` Thomas Gleixner
2016-01-26 23:29 ` David Rientjes
2016-01-26 23:29 ` David Rientjes
2016-01-27 0:19 ` Joonsoo Kim [this message]
2016-01-27 0:36 ` David Rientjes
2016-01-27 0:36 ` David Rientjes
2016-01-27 0:59 ` Joonsoo Kim
2016-01-27 7:59 ` Christian Borntraeger
2016-01-27 7:59 ` Christian Borntraeger
2016-01-27 12:41 ` Vlastimil Babka
2016-01-27 12:47 ` Christian Borntraeger
2016-01-27 12:47 ` Christian Borntraeger
2016-01-27 13:03 ` Vlastimil Babka
2016-01-27 13:09 ` Christian Borntraeger
2016-01-28 4:25 ` Joonsoo Kim
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=20160127001918.GA7089@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=heiko.carstens@de.ibm.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=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).