LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev@gmail.com>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 00/26] Dynamic kernel command-line
Date: Sat, 2 Dec 2006 12:47:41 +0200 [thread overview]
Message-ID: <200612021247.43291.alon.barlev@gmail.com> (raw)
Hello,
This is take 3 of submission, I submit this patch
once in a few monthes to collect some more signatures :)
Until now, I got three:
- avr32
- sh
- sh64
I know this is not one of major priorities, but it
should be simple enough to be reviewed and included.
I will also be happy to get a REJECT response, so I
stop trying to get it included. Any suggestions of
how to push this farward will also be appreciated.
Current implementation stores a static command-line
buffer allocated to COMMAND_LINE_SIZE size. Most
architectures stores two copies of this buffer, one
for future reference and one for parameter parsing.
Current kernel command-line size for most architecture
is much too small for module parameters, video settings,
initramfs paramters and much more. The problem is that
setting COMMAND_LINE_SIZE to a grater value, allocates
static buffers.
In order to allow a greater command-line size, these
buffers should be dynamically allocated or marked
as init disposable buffers, so unused memory can be
released.
This patch renames the static saved_command_line
variable into boot_command_line adding __initdata
attribute, so that it can be disposed after
initialization. This rename is required so applications
that use saved_command_line will not be affected
by this change.
It reintroduces saved_command_line as dynamically
allocated buffer to match the data in boot_command_line.
It also mark secondary command-line buffer as __initdata,
and copies it to dynamically allocated static_command_line
buffer components may hold reference to it after
initialization.
This patch is for linux-2.6.19 and is divided to
target each architecture. I could not check this in any
architecture so please forgive me if I got it wrong.
The per-architecture modification is very simple, use
boot_command_line in place of saved_command_line. The
common code is the change into dynamic command-line.
Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>
---
next reply other threads:[~2006-12-02 10:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 10:47 Alon Bar-Lev [this message]
2006-12-02 10:48 ` [PATCH 01/26] Dynamic kernel command-line - common Alon Bar-Lev
2006-12-02 10:48 ` [PATCH 02/26] Dynamic kernel command-line - alpha Alon Bar-Lev
2006-12-02 10:49 ` [PATCH 03/26] Dynamic kernel command-line - arm Alon Bar-Lev
2006-12-02 10:49 ` [PATCH 04/26] Dynamic kernel command-line - arm26 Alon Bar-Lev
2006-12-02 10:49 ` [PATCH 05/26] Dynamic kernel command-line - avr32 Alon Bar-Lev
2006-12-02 10:50 ` [PATCH 06/26] Dynamic kernel command-line - cris Alon Bar-Lev
2006-12-02 10:50 ` [PATCH 07/26] Dynamic kernel command-line - frv Alon Bar-Lev
2006-12-02 10:50 ` [PATCH 08/26] Dynamic kernel command-line - h8300 Alon Bar-Lev
2006-12-02 10:51 ` [PATCH 09/26] Dynamic kernel command-line - i386 Alon Bar-Lev
2006-12-02 10:51 ` [PATCH 10/26] Dynamic kernel command-line - ia64 Alon Bar-Lev
2006-12-02 10:52 ` [PATCH 11/26] Dynamic kernel command-line - m32r Alon Bar-Lev
2006-12-02 10:52 ` [PATCH 12/26] Dynamic kernel command-line - m68k Alon Bar-Lev
2006-12-02 10:53 ` [PATCH 13/26] Dynamic kernel command-line - m68knommu Alon Bar-Lev
2006-12-02 10:53 ` [PATCH 14/26] Dynamic kernel command-line - mips Alon Bar-Lev
2006-12-02 10:53 ` [PATCH 15/26] Dynamic kernel command-line - parisc Alon Bar-Lev
2006-12-02 10:54 ` [PATCH 16/26] Dynamic kernel command-line - powerpc Alon Bar-Lev
2006-12-02 10:54 ` [PATCH 17/26] Dynamic kernel command-line - ppc Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 18/26] Dynamic kernel command-line - s390 Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 20/26] Dynamic kernel command-line - sh64 Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 21/26] Dynamic kernel command-line - sparc Alon Bar-Lev
2006-12-02 10:56 ` [PATCH 22/26] Dynamic kernel command-line - sparc64 Alon Bar-Lev
2006-12-02 10:56 ` [PATCH 23/26] Dynamic kernel command-line - um Alon Bar-Lev
2006-12-02 10:56 ` [PATCH 24/26] Dynamic kernel command-line - v850 Alon Bar-Lev
2006-12-02 10:57 ` [PATCH 25/26] Dynamic kernel command-line - x86_64 Alon Bar-Lev
2006-12-02 10:58 ` [PATCH 26/26] Dynamic kernel command-line - xtensa Alon Bar-Lev
-- strict thread matches above, loose matches on Subject: below --
2007-01-18 12:58 [patch 00/26] Dynamic kernel command-line Bernhard Walle
2006-09-03 21:50 [PATCH " Alon Bar-Lev
2006-09-03 23:33 ` Paul Mackerras
2006-09-04 2:50 ` Nigel Cunningham
2006-09-04 8:32 ` Martin Schwidefsky
2006-09-04 8:42 ` Alon Bar-Lev
2006-09-04 5:05 ` Alon Bar-Lev
2006-09-04 6:12 ` Andi Kleen
2006-09-04 17:09 ` Luca
2006-09-04 1:01 ` Josh Boyer
2006-09-04 5:07 ` Alon Bar-Lev
2006-09-04 19:59 ` Josh Boyer
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=200612021247.43291.alon.barlev@gmail.com \
--to=alon.barlev@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH 00/26] Dynamic kernel command-line' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).