From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hbabu@us.ibm.com" <hbabu@us.ibm.com>,
"Huang, Ying" <ying.huang@intel.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"sam@ravnborg.org" <sam@ravnborg.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH 00/14] RFC: x86: relocatable kernel changes
Date: Fri, 08 May 2009 11:47:47 -0700 [thread overview]
Message-ID: <4A047E53.8040003@intel.com> (raw)
In-Reply-To: <m1tz3wgk3n.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
>
> Perhaps we should have:
> init_size
> best start (As a 64bit field please)
> optimum align (Or we flip it around)
>
Thinking about this some more, I think you have a very good idea here.
Specifically, if we retcon the existing kernel_alignment field as
"preferred alignment" (ignoring the naming issue for a bit), we can set
that to 16 MB, which should give us correct behavior for all previously
existing bootloaders. Then we create a new "minimum alignment" field
that newer bootloaders can use to relax the alignment requirement -- all
the way down to 4K in the case of i386. We document this field
indicating that the bootloader should find the highest power of 2 <=
preferred alignment, but down to this number.
The preferred address field becomes a readonly, advisory field; with it
being readonly there aren't any funny issues with a strange loader
writing a 64-bit address for a kernel which can't handle it (64-bit
loading will still need substantial protocol changes, including how to
find the entry point.)
Does that work for you? That *should* address all your concerns, right?
-hpa
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"hbabu@us.ibm.com" <hbabu@us.ibm.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"Huang, Ying" <ying.huang@intel.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"sam@ravnborg.org" <sam@ravnborg.org>
Subject: Re: [PATCH 00/14] RFC: x86: relocatable kernel changes
Date: Fri, 08 May 2009 11:47:47 -0700 [thread overview]
Message-ID: <4A047E53.8040003@intel.com> (raw)
In-Reply-To: <m1tz3wgk3n.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
>
> Perhaps we should have:
> init_size
> best start (As a 64bit field please)
> optimum align (Or we flip it around)
>
Thinking about this some more, I think you have a very good idea here.
Specifically, if we retcon the existing kernel_alignment field as
"preferred alignment" (ignoring the naming issue for a bit), we can set
that to 16 MB, which should give us correct behavior for all previously
existing bootloaders. Then we create a new "minimum alignment" field
that newer bootloaders can use to relax the alignment requirement -- all
the way down to 4K in the case of i386. We document this field
indicating that the bootloader should find the highest power of 2 <=
preferred alignment, but down to this number.
The preferred address field becomes a readonly, advisory field; with it
being readonly there aren't any funny issues with a strange loader
writing a 64-bit address for a kernel which can't handle it (64-bit
loading will still need substantial protocol changes, including how to
find the entry point.)
Does that work for you? That *should* address all your concerns, right?
-hpa
next prev parent reply other threads:[~2009-05-08 18:48 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 22:26 [PATCH 00/14] RFC: x86: relocatable kernel changes H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 01/14] x86, boot: align the .bss section in the decompressor H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:17 ` Sam Ravnborg
2009-05-08 7:17 ` Sam Ravnborg
2009-05-08 8:18 ` Eric Dumazet
2009-05-08 8:18 ` Eric Dumazet
2009-05-08 16:54 ` H. Peter Anvin
2009-05-08 16:54 ` H. Peter Anvin
2009-05-08 7:53 ` Cyrill Gorcunov
2009-05-08 7:53 ` Cyrill Gorcunov
2009-05-08 17:03 ` H. Peter Anvin
2009-05-08 17:03 ` H. Peter Anvin
2009-05-08 17:15 ` Cyrill Gorcunov
2009-05-08 17:15 ` Cyrill Gorcunov
2009-05-08 17:21 ` H. Peter Anvin
2009-05-08 17:21 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 02/14] x86, boot: honor CONFIG_PHYSICAL_START when relocatable H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:34 ` Sam Ravnborg
2009-05-08 7:34 ` Sam Ravnborg
2009-05-08 16:58 ` H. Peter Anvin
2009-05-08 16:58 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 03/14] x86, config: change defaults PHYSICAL_START and PHYSICAL_ALIGN H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:36 ` Sam Ravnborg
2009-05-08 7:36 ` Sam Ravnborg
2009-05-08 9:47 ` Ingo Molnar
2009-05-08 9:47 ` Ingo Molnar
2009-05-08 17:01 ` H. Peter Anvin
2009-05-08 17:01 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 04/14] x86, boot: unify use LOAD_PHYSICAL_ADDR and LOAD_PHYSICAL_ALIGN H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 05/14] kbuild: allow compressors (gzip, bzip2, lzma) to take multiple inputs H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:42 ` Sam Ravnborg
2009-05-08 7:42 ` Sam Ravnborg
2009-05-08 20:18 ` H. Peter Anvin
2009-05-08 20:18 ` H. Peter Anvin
2009-05-08 20:47 ` Sam Ravnborg
2009-05-08 20:47 ` Sam Ravnborg
2009-05-08 20:49 ` H. Peter Anvin
2009-05-08 20:49 ` H. Peter Anvin
2009-05-08 21:33 ` Sam Ravnborg
2009-05-08 21:33 ` Sam Ravnborg
2009-05-07 22:26 ` [PATCH 06/14] x86: add a Kconfig symbol for when relocations are needed H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 07/14] x86, boot: simplify arch/x86/boot/compressed/Makefile H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:45 ` Sam Ravnborg
2009-05-08 7:45 ` Sam Ravnborg
2009-05-07 22:26 ` [PATCH 08/14] x86, boot: use BP_scratch in arch/x86/boot/compressed/head_*.S H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 09/14] x86, boot: add new runtime_address and runtime_size bzImage fields H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-08 7:55 ` Sam Ravnborg
2009-05-08 7:55 ` Sam Ravnborg
2009-05-08 21:09 ` H. Peter Anvin
2009-05-08 21:09 ` H. Peter Anvin
2009-05-08 21:35 ` Sam Ravnborg
2009-05-08 21:35 ` Sam Ravnborg
2009-05-07 22:26 ` [PATCH 10/14] x86, doc: document the runtime_start " H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:26 ` [PATCH 11/14] x86, boot: use rep movsq to move kernel on 64 bits H. Peter Anvin
2009-05-07 22:26 ` H. Peter Anvin
2009-05-07 22:27 ` [PATCH 12/14] x86, boot: zero EFLAGS on 32 bits H. Peter Anvin
2009-05-07 22:27 ` H. Peter Anvin
2009-05-07 22:27 ` [PATCH 13/14] x86: make CONFIG_RELOCATABLE the default H. Peter Anvin
2009-05-07 22:27 ` H. Peter Anvin
2009-05-07 22:27 ` [PATCH 14/14] x86, defconfig: update defconfigs to relocatable H. Peter Anvin
2009-05-07 22:27 ` H. Peter Anvin
2009-05-08 1:23 ` [PATCH 00/14] RFC: x86: relocatable kernel changes Eric W. Biederman
2009-05-08 1:23 ` Eric W. Biederman
2009-05-08 5:31 ` H. Peter Anvin
2009-05-08 5:31 ` H. Peter Anvin
2009-05-08 6:54 ` Eric W. Biederman
2009-05-08 6:54 ` Eric W. Biederman
2009-05-08 18:04 ` H. Peter Anvin
2009-05-08 18:04 ` H. Peter Anvin
2009-05-08 18:47 ` H. Peter Anvin [this message]
2009-05-08 18:47 ` H. Peter Anvin
2009-05-11 5:18 ` RFC: x86: relocatable kernel changes (revised spec) H. Peter Anvin
2009-05-11 5:18 ` H. Peter Anvin
2009-05-11 11:54 ` Eric W. Biederman
2009-05-11 11:54 ` Eric W. Biederman
2009-05-11 16:03 ` H. Peter Anvin
2009-05-11 16:03 ` H. Peter Anvin
2009-05-11 17:56 ` RFC: x86: relocatable kernel changes (revised spec v2) H. Peter Anvin
2009-05-11 17:56 ` H. Peter Anvin
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=4A047E53.8040003@intel.com \
--to=h.peter.anvin@intel.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=hpa@linux.intel.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.