From: Oleg Verych <olecom@flower.upol.cz>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
Date: Tue, 9 Oct 2007 13:44:47 +0200 [thread overview]
Message-ID: <E1IfDW3-0001qA-9c@flower> (raw)
In-Reply-To: <1191920123.9719.71.camel@caritas-dev.intel.com>
* Tue, 09 Oct 2007 16:55:23 +0800
>
> On Tue, 2007-10-09 at 02:06 +1000, Nick Piggin wrote:
>> On Tuesday 09 October 2007 18:22, Huang, Ying wrote:
[]
>> I'm just wondering whether you really need to access highmem in
>> boot code...
>
> Because the zero page (boot_parameters) of i386 boot protocol has 4k
> limitation, a linked list style boot parameter passing mechanism (struct
> setup_data) is proposed by Peter Anvin. The linked list is provided by
> bootloader, so it is possible to be in highmem region.
Can it be explained, why boot protocol and boot line must be expanded?
This amount of code for what?
arch/i386/Kconfig | 3 -
arch/i386/boot/header.S | 8 +++
arch/i386/kernel/setup.c | 92 +++++++++++++++++++++++++++++++++++++++++++
arch/x86_64/kernel/setup.c | 37 +++++++++++++++++
include/asm-i386/bootparam.h | 15 +++++++
include/asm-i386/io.h | 7 +++
include/linux/mm.h | 2
mm/memory.c | 24 +++++++++++
If it is proposed for passing ACPI makeup language bugfixes by boot
line for ACPI parser in the kernel, or "telling to kernel what to do
via EFI" then it's kind of very nasty red flag.
I'd suggest to have initramfs image ready with all possible
data/options/actions based on very small amount of possible boot line
information.
Any _right_ use-cases explained for dummies are appreciated.
Thanks.
--
-o--=O`C
#oo'L O
<___=E M
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-09 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1191912010.9719.18.camel@caritas-dev.intel.com>
2007-10-08 15:25 ` [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data Nick Piggin
2007-10-09 8:22 ` Huang, Ying
2007-10-08 16:06 ` Nick Piggin
2007-10-09 8:55 ` Huang, Ying
2007-10-08 16:28 ` Nick Piggin
2007-10-09 9:26 ` Huang, Ying
2007-10-09 11:44 ` Oleg Verych [this message]
2007-10-09 11:13 ` Andi Kleen
2007-10-09 14:00 ` huang ying
2007-10-09 14:04 ` 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=E1IfDW3-0001qA-9c@flower \
--to=olecom@flower.upol.cz \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mouli@linux.intel.com \
--cc=nickpiggin@yahoo.com.au \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).