From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: reservetop fix disables mem=
Date: Sat, 19 Sep 2009 20:32:24 +0200 [thread overview]
Message-ID: <20090919183224.GA3038@elte.hu> (raw)
In-Reply-To: <4AB51DFD.2000904@kernel.org>
* Yinghai Lu <yinghai@kernel.org> wrote:
> Yinghai Lu wrote:
> > Ingo Molnar wrote:
> >> I thoroughly zapped it. Do you know about any commit ID where it snuck
> >> in?
> >
> > after close looking, it will break
> > 1. some cpu feature in early stage too, like cpu_has_x2apic
> > 2. will break built-in-command line
> > 3. will break other memmap= and mem=
> > 4. early_dbgp and early_console that will use early_ioremap to access mmio (?)
thanks Yinghai - i have queued up your revert. Thanks Hugh for noticing
it!
> after revet it, it seem mem=32g etc still broken, maybe some other
> commit about x86 platform support from Thomas broke it.
Thomas?
Ingo
next prev parent reply other threads:[~2009-09-19 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 16:45 linux-next: reservetop fix disables mem= Hugh Dickins
2009-08-24 17:38 ` Yinghai Lu
2009-08-24 18:27 ` Ingo Molnar
2009-08-28 19:28 ` Yinghai Lu
2009-09-06 6:56 ` Yinghai Lu
2009-09-16 0:23 ` Hugh Dickins
2009-09-19 17:55 ` Ingo Molnar
2009-09-19 18:02 ` Yinghai Lu
2009-09-19 18:07 ` Yinghai Lu
2009-09-19 18:32 ` Ingo Molnar [this message]
2009-09-19 18:33 ` [tip:x86/urgent] Revert 'x86: Fix system crash when loading with "reservetop" parameter' tip-bot for Yinghai Lu
2009-08-26 1:13 ` linux-next: reservetop fix disables mem= Xiao Guangrong
2009-09-01 7:55 ` [RFC][PATCH] x86: introduce parse_early_param_alone() to parse param early (Was Re: linux-next: reservetop fix disables mem= ) Xiao Guangrong
2009-09-01 15:17 ` Américo Wang
2009-09-03 6:04 ` Xiao Guangrong
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=20090919183224.GA3038@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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