From: Gary Hade <garyhade@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Gary Hade <garyhade@us.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
lcm@us.ibm.com
Subject: Re: x86_64: remove debug code from arch_add_memory()
Date: Wed, 29 Oct 2008 09:43:06 -0700 [thread overview]
Message-ID: <20081029164305.GA9035@us.ibm.com> (raw)
In-Reply-To: <20081029083053.GB6364@elte.hu>
On Wed, Oct 29, 2008 at 09:30:53AM +0100, Ingo Molnar wrote:
>
> * Gary Hade <garyhade@us.ibm.com> wrote:
>
> >
> > Gets rid of dmesg spam created during physical memory hot-add which
> > will very likely confuse users. The change removes what appears to
> > be debugging code which I assume was unintentionally included in:
> > x86: arch/x86/mm/init_64.c printk fixes
> > commit 10f22dde556d1ed41d55355d1fb8ad495f9810c8
> >
> > Signed-off-by: Gary Hade <garyhade@us.ibm.com>
> >
> > ---
> > arch/x86/mm/init_64.c | 1 -
> > 1 file changed, 1 deletion(-)
>
> applied to tip/x86/urgent, thanks Gary!
>
> Note, i changed it slightly: instead of removing it completely i
> changed it to WARN_ON_ONCE(ret), to show us when __add_pages() fails.
> (which is what the original intention was there)
No problem! That's obviously better.
> This does not trigger in your tests, right?
Correct. I just did a memory hot-add with that change and the
WARN_ON_ONCE(ret) did not write anything to dmesg.
Thanks,
Gary
--
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503 IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc
prev parent reply other threads:[~2008-10-29 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 23:43 x86_64: remove debug code from arch_add_memory() Gary Hade
2008-10-29 8:30 ` Ingo Molnar
2008-10-29 16:43 ` Gary Hade [this message]
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=20081029164305.GA9035@us.ibm.com \
--to=garyhade@us.ibm.com \
--cc=hpa@zytor.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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