From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: Kexec command line length
Date: Tue, 29 Jan 2008 19:17:01 +0100 [thread overview]
Message-ID: <20080129181701.GB535@suse.de> (raw)
In-Reply-To: <20080129154104.GA12219@redhat.com>
* Vivek Goyal <vgoyal@redhat.com> [2008-01-29 16:41]:
>
> I think 2048 command line support came much later. I think it came between
> version 2.05 and 2.06 (But somebody needs to dive into archive to verify).
> Because command line size could go beyond 256, we introduced cmdline_size
> parameter in version 2.06 to let a boot loader know.
Large command line support was added with
cca97de1184f6000d22b4106d47687b31cca1fa3
v2.6.20-1929-gcca97de
which means that it was merged 2.6.21.
> What Bernanrd seems to be talking about a small window where boot protocol
> was 2.05 but supported command line size was still 2048.
2.05 was added with
be274eeaf20b4c7155242645d5e2c48b023e609b
v2.6.19-1394-gbe274ee
which means that it was merged 2.6.20. But it got implemented for i386
only that time, so x86_64 still had the 2.04 version.
The command line length in the boot protocol was added with
8f9aeca7a081d81c4c9862be1e04f15b5ab5461f
v2.6.21-1864-g8f9aeca
which menas that it was merged 2.6.22.
> if (protocol version > 2.06)
> error user depending on cmdline_size;
> else if (protocol version > 2.05 && protocol version < 2.06)
> warn on cmdline being more than 256. We don't know for sure.
> else
> error out if cmdline is greater than 256
The problem is 2.6.21: It had on x86_64 2.04 boot protocol but
2048 command line size. I just verified this via the tarball. :(
Maybe it could be implemented with versions ...
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-01-29 18:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 13:43 Kexec command line length Neil Horman
2008-01-14 14:50 ` Bernhard Walle
2008-01-14 15:40 ` Neil Horman
2008-01-15 15:27 ` Vivek Goyal
2008-01-15 17:09 ` Neil Horman
2008-01-15 17:37 ` Vivek Goyal
2008-01-25 12:35 ` Neil Horman
2008-01-25 15:39 ` Vivek Goyal
2008-01-25 15:44 ` H. Peter Anvin
2008-01-25 19:50 ` Neil Horman
2008-01-25 19:54 ` H. Peter Anvin
2008-01-25 20:11 ` Neil Horman
2008-01-25 20:13 ` Vivek Goyal
2008-01-25 20:54 ` Neil Horman
2008-01-28 17:08 ` Neil Horman
2008-01-28 19:37 ` Vivek Goyal
2008-01-28 20:07 ` Neil Horman
2008-01-28 20:20 ` Vivek Goyal
2008-01-28 20:53 ` Neil Horman
2008-01-28 21:09 ` Vivek Goyal
2008-01-28 21:29 ` Bernhard Walle
2008-01-29 1:01 ` Neil Horman
2008-01-29 15:41 ` Vivek Goyal
2008-01-29 18:17 ` Bernhard Walle [this message]
2008-01-29 18:52 ` Neil Horman
2008-01-29 19:57 ` Neil Horman
2008-01-30 20:53 ` Vivek Goyal
2008-01-30 20:59 ` Neil Horman
2008-01-30 21:08 ` Vivek Goyal
2008-01-30 21:18 ` Neil Horman
2008-01-30 21:45 ` Vivek Goyal
2008-01-31 0:10 ` Neil Horman
2008-01-31 7:16 ` Bernhard Walle
2008-02-12 21:11 ` Neil Horman
2008-02-18 3:14 ` Simon Horman
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=20080129181701.GB535@suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=nhorman@tuxdriver.com \
--cc=vgoyal@redhat.com \
/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