From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Hugh Dickins <hugh@veritas.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: parsing mem=700M broken
Date: Tue, 23 Dec 2008 15:33:27 +0100 [thread overview]
Message-ID: <20081223143327.GF29151@elte.hu> (raw)
In-Reply-To: <86802c440812222152yd000009yf890f5cd303860e4@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org> wrote:
> On Mon, Dec 22, 2008 at 7:06 PM, Hugh Dickins <hugh@veritas.com> wrote:
> > Hi Rusty,
> >
> > I find that bootparam "mem=700M" isn't working in linux-next or mmotm,
> > and have bisected it down to your patch below; but now I'm off to bed
> > without working out just what goes wrong (I'll bet it's the "=").
> >
> > Hugh
> >
> > commit 5c886584a758edba7e25ad9df974cf15a4a1f59d
> > Author: Rusty Russell <rusty@rustcorp.com.au>
> > Date: Wed Dec 3 13:34:34 2008 +1030
> >
> > Call early_param earlier.
> >
> > We delete all the arch calls: we call it from start_kernel earlier
> > now. We also no longer take a temporary copy, but parse in place.
> >
> > Note: IA64 needs to parse "machvec=" before other commandline options
> > but machvec_init_from_cmdline() needs efi_init() and io_port_init(),
> > so they are all moved into arch_get_boot_command_line().
> >
>
> yeah, you are right.
>
> static int __init parse_memopt(char *p)
> {
> u64 mem_size;
>
> if (!p)
> return -EINVAL;
>
> #ifdef CONFIG_X86_32
> if (!strcmp(p, "nopentium")) {
> setup_clear_cpu_cap(X86_FEATURE_PSE);
> return 0;
> }
> #endif
>
> userdef = 1;
> mem_size = memparse(p, &p);
> e820_remove_range(mem_size, ULLONG_MAX - mem_size, E820_RAM, 1);
>
> return 0;
> }
> early_param("mem", parse_memopt);
>
>
> in x86 we use that param analyser much later ( after we check the e820
> table..)
>
> other cpu flag will be overwrite too..
>
> anyway, this patch is not go through x86 tip..., some strange!
the x86 impact is incidental:
arch/avr32/kernel/setup.c | 2 --
arch/ia64/kernel/setup.c | 18 ++++++++----------
arch/m68k/kernel/setup.c | 2 --
arch/mips/kernel/setup.c | 2 --
arch/powerpc/kernel/prom.c | 1 -
arch/s390/kernel/setup.c | 2 --
arch/sh/kernel/setup.c | 2 --
arch/sparc/kernel/setup.c | 3 ---
arch/sparc64/kernel/setup.c | 3 ---
arch/x86/kernel/setup.c | 3 ---
include/linux/init.h | 2 --
init/main.c | 21 ++++-----------------
12 files changed, 12 insertions(+), 49 deletions(-)
we generally do not require patches to go via the x86 tree that just
happen to touch it with the intention of not breaking anything.
Rusty, will you fix or revert it?
Ingo
next prev parent reply other threads:[~2008-12-23 14:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 3:06 linux-next: parsing mem=700M broken Hugh Dickins
2008-12-23 5:52 ` Yinghai Lu
2008-12-23 14:33 ` Ingo Molnar [this message]
2008-12-24 7:38 ` Rusty Russell
2008-12-24 8:09 ` Yinghai Lu
2008-12-24 23:09 ` Yinghai Lu
2008-12-25 11:40 ` Rusty Russell
2008-12-25 22:46 ` Yinghai Lu
2008-12-24 12:30 ` Ingo Oeser
2008-12-25 5:50 ` Rusty Russell
2008-12-24 14:44 ` Hugh Dickins
2008-12-25 3:28 ` Rusty Russell
2008-12-27 13:12 ` Rusty Russell
2008-12-28 0:43 ` Hugh Dickins
2008-12-28 2:07 ` Yinghai Lu
2009-01-01 3:42 ` Rusty Russell
2008-12-25 12:17 ` [RFC] boot parameter handling cleanup II Rusty Russell
2008-12-25 12:20 ` [RFC PATCH] param: start_kernel_with_args() Rusty Russell
2008-12-27 10:14 ` [RFC] boot parameter handling cleanup II 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=20081223143327.GF29151@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--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