All of lore.kernel.org
 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] mm,x86: initialize high mem before free_all_bootmem()
Date: Tue, 6 Dec 2011 11:36:18 +0100	[thread overview]
Message-ID: <20111206103618.GE15966@elte.hu> (raw)
In-Reply-To: <20111206102622.GC3105@redhat.com>


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

> On Tue, Dec 06, 2011 at 09:25:55AM +0100, Ingo Molnar wrote:
> > The thing is, the pagealloc bug you fixed basically kept 
> > pagealloc debugging essentially disabled for a really long time, 
> > correct?
> Yes, it worked only in special cases.
>  
> > So i'd expect there to be quite a few latent problems - 
> > i'll give it some more testing before pushing out the result.
>
> Ehh, I expect them too, but fortunately only with 
> CONFIG_DEBUG_PAGEALLOC, non-debug kernel are not affected.

I test DEBUG_PAGEALLOC=y kernels all the time - i just booted a 
32-bit and a 64-bit allyesconfig kernel an hour ago.

Miraculously everything appears to be in working order so far.

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>

WARNING: multiple messages have this Message-ID (diff)
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] mm,x86: initialize high mem before free_all_bootmem()
Date: Tue, 6 Dec 2011 11:36:18 +0100	[thread overview]
Message-ID: <20111206103618.GE15966@elte.hu> (raw)
In-Reply-To: <20111206102622.GC3105@redhat.com>


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

> On Tue, Dec 06, 2011 at 09:25:55AM +0100, Ingo Molnar wrote:
> > The thing is, the pagealloc bug you fixed basically kept 
> > pagealloc debugging essentially disabled for a really long time, 
> > correct?
> Yes, it worked only in special cases.
>  
> > So i'd expect there to be quite a few latent problems - 
> > i'll give it some more testing before pushing out the result.
>
> Ehh, I expect them too, but fortunately only with 
> CONFIG_DEBUG_PAGEALLOC, non-debug kernel are not affected.

I test DEBUG_PAGEALLOC=y kernels all the time - i just booted a 
32-bit and a 64-bit allyesconfig kernel an hour ago.

Miraculously everything appears to be in working order so far.

Thanks,

	Ingo

  reply	other threads:[~2011-12-06 10:38 UTC|newest]

Thread overview: 18+ 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-11-29 16:05 ` Stanislaw Gruszka
2011-12-05 11:06 ` Ingo Molnar
2011-12-05 15:00   ` Stanislaw Gruszka
2011-12-05 15:54     ` Ingo Molnar
2011-12-05 15:54       ` Ingo Molnar
2011-12-06  7:55       ` Stanislaw Gruszka
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:08           ` Stanislaw Gruszka
2011-12-06  8:25           ` Ingo Molnar
2011-12-06  8:25             ` Ingo Molnar
2011-12-06 10:26             ` Stanislaw Gruszka
2011-12-06 10:26               ` Stanislaw Gruszka
2011-12-06 10:36               ` Ingo Molnar [this message]
2011-12-06 10:36                 ` Ingo Molnar
2011-12-06  9:58           ` [tip:x86/mm] x86/mm: Initialize " tip-bot for Stanislaw Gruszka
2011-12-06  9:59 ` [tip:x86/mm] mm, x86: Remove debug_pagealloc_enabled tip-bot for Stanislaw Gruszka

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=20111206103618.GE15966@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.