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 09:25:55 +0100 [thread overview]
Message-ID: <20111206082555.GA28314@elte.hu> (raw)
In-Reply-To: <20111206080833.GB3105@redhat.com>
* Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> Patch fixes boot crash with my previous patch "mm,x86: remove
> debug_pagealloc_enabled" applied:
Great, thanks - i've started testing of your pagealloc
restoration patch again.
> Would be good to apply this patch before "mm,x86: remove
> debug_pagealloc_enabled" to prevent problem be possibly
> observable during bisection.
Yep, applied them in that order.
The thing is, the pagealloc bug you fixed basically kept
pagealloc debugging essentially disabled for a really long time,
correct? So i'd expect there to be quite a few latent problems -
i'll give it some more testing before pushing out the result.
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>
next prev parent reply other threads:[~2011-12-06 8:27 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
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 [this message]
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=20111206082555.GA28314@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).