From: "Keith Mannthey" <kmannth@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Hugh Dickins" <hugh@veritas.com>,
"Andrew Morton" <akpm@osdl.org>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Andi Kleen" <ak@suse.de>,
linux-kernel@vger.kernel.org, apw@shadowen.org
Subject: Re: 2.6.18-rc3-mm2 early_param mem= fix
Date: Tue, 8 Aug 2006 17:10:33 -0700 [thread overview]
Message-ID: <a762e240608081710h532f6bbl7a1670537fd481bd@mail.gmail.com> (raw)
In-Reply-To: <m13bc8b6ca.fsf@ebiederm.dsl.xmission.com>
On 8/7/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Hugh Dickins <hugh@veritas.com> writes:
>
> > On Sun, 6 Aug 2006, Hugh Dickins wrote:
> >> I was impressed by how fast 2.6.18-rc3-mm2 is under memory pressure,
> >> until I noticed that my "mem=512M" boot option was doing nothing. The
> >> two fixes below got it working, but I wonder how many other early_param
> >> "option=" args are wrong (e.g. "memmap=" in the same file): x86_64
> >> shows many such, i386 shows only one, I've not followed it up further.
> >
> > Oh, and that's not enough for it to show up in x86_64's /proc/cmdline.
>
> The /proc/cmdline part is easy.
>
> Someone deleted the copy from saved_command_line to command_line.
> Since kernel/params.c:parse_args called in init/main.c is destructive
> if we don't do this we will never see a reasonable command line in /proc,
> and /init implementations that parse /proc/command_line will choke horribly.
>
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
>
> diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c
> index 3bc1ff4..37206a4 100644
> --- a/arch/x86_64/kernel/setup.c
> +++ b/arch/x86_64/kernel/setup.c
> @@ -378,7 +378,8 @@ #endif
> early_identify_cpu(&boot_cpu_data);
>
> parse_early_param();
> - *cmdline_p = saved_command_line;
> + memcpy(command_line, saved_command_line, COMMAND_LINE_SIZE);
> + *cmdline_p = command_line;
>
> finish_e820_parsing();
Ok this helped keep the cmdline around but the early_param is still
busted with 2.6.18-rc3-mm2 (I don't have cmdline problem with non -mm
2.6.18-rc3).
I am booting with numa=hotadd=100 on x86_64. The parameter
hotadd_percent is not getting setup right. Printk tells me that
numa_setup is not called during boot.
if I change
early_param("numa=", numa_setup);
to
early_param("numa", numa_setup);
The parameter hotadd_percent is setup right but there is a
"Malformed early option 'numa'" message.
Is there some other patch that I missed to fix this?
Also it seems like the earlyconsole isn't getting setup right.... It
seems to take forever to start (say about 20-30 seconds) This pause in
the boot is caused by the reserve hot-add patch but early console
should start before the pause.
command line is root=/dev/sda3
ip=9.47.66.153:9.47.66.169:9.47.66.1:255.255.255.0 resume=/dev/sda2
showopts earlyprintk=ttyS0,115200 console=ttyS0,115200 console=tty0
debug numa=hotadd=100
Again thing work as expected with 2.6.18-rc3.
Thanks,
Keith
next prev parent reply other threads:[~2006-08-09 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 17:22 Hugh Dickins
2006-08-06 17:31 ` Hugh Dickins
2006-08-07 15:08 ` Andy Whitcroft
2006-08-07 21:09 ` Eric W. Biederman
2006-08-09 0:10 ` Keith Mannthey [this message]
2006-08-09 1:03 ` Andi Kleen
2006-08-09 1:27 ` Rusty Russell
2006-08-06 19:15 ` Andrew Morton
2006-08-07 2:06 ` Andi Kleen
2006-08-07 2:54 ` Rusty Russell
2006-08-07 2:55 ` Andi Kleen
2006-08-07 3:08 ` Rusty Russell
2006-08-07 3:13 ` Andi Kleen
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=a762e240608081710h532f6bbl7a1670537fd481bd@mail.gmail.com \
--to=kmannth@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=ebiederm@xmission.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome