linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org,
	Mel Gorman <mgorman@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH repost] mm,x86: remove debug_pagealloc_enabled
Date: Mon, 5 Dec 2011 16:54:34 +0100	[thread overview]
Message-ID: <20111205155434.GD30287@elte.hu> (raw)
In-Reply-To: <20111205150019.GA5434@redhat.com>


* Stanislaw Gruszka <sgruszka@redhat.com> wrote:

> On Mon, Dec 05, 2011 at 12:06:56PM +0100, Ingo Molnar wrote:
> > 
> > * Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > 
> > > When (no)bootmem finish operation, it pass pages to buddy allocator.
> > > Since debug_pagealloc_enabled is not set, we will do not protect pages,
> > > what is not what we want with CONFIG_DEBUG_PAGEALLOC=y.
> > > 
> > > To fix remove debug_pagealloc_enabled. That variable was introduced by
> > > commit 12d6f21e "x86: do not PSE on CONFIG_DEBUG_PAGEALLOC=y" to get
> > > more CPA (change page attribude) code testing. But currently we have
> > > CONFIG_CPA_DEBUG, which test CPA.
> > > 
> > > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > > Acked-by: Mel Gorman <mgorman@suse.de>
> > > ---
> > >  arch/x86/mm/pageattr.c |    6 ------
> > >  include/linux/mm.h     |   10 ----------
> > >  init/main.c            |    5 -----
> > >  mm/debug-pagealloc.c   |    3 ---
> > >  4 files changed, 0 insertions(+), 24 deletions(-)
> > 
> > I'm getting this boot crash with the patch applied:
> 
> I'm sorry for breaking the boot. I tried to reproduce problem 
> on my laptop, but failed. I plan to test patch with your 
> config on some other machines.
> 
> On the meantime can you test attached incremental patch and 
> see if it workaround the crash? I suspect memblock reuse pages 
> that it passed already to buddy allocator.

That will take some time - so if you could try my config on 
another box that would be great. There isnt anything special 
about that box.

Thanks,

	Ingo

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-12-05 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 16:05 [PATCH repost] mm,x86: remove debug_pagealloc_enabled Stanislaw Gruszka
2011-12-05 11:06 ` Ingo Molnar
2011-12-05 15:00   ` Stanislaw Gruszka
2011-12-05 15:54     ` Ingo Molnar [this message]
2011-12-06  7:55       ` Stanislaw Gruszka
2011-12-06  8:08         ` [PATCH] mm,x86: initialize high mem before free_all_bootmem() Stanislaw Gruszka
2011-12-06  8:25           ` Ingo Molnar
2011-12-06 10:26             ` Stanislaw Gruszka
2011-12-06 10:36               ` Ingo Molnar

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=20111205155434.GD30287@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=sgruszka@redhat.com \
    --cc=tglx@linutronix.de \
    --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).