From: ebiederm@xmission.com (Eric W. Biederman)
To: "Huang, Ying" <ying.huang@intel.com>
Cc: ak@suse.de, akpm@linux-foundation.org,
Yinghai Lu <yhlu.kernel@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document
Date: Wed, 01 Aug 2007 11:16:43 -0600 [thread overview]
Message-ID: <m1r6mnnpj8.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1185865087.23149.50.camel@caritas-dev.intel.com> (Ying Huang's message of "Tue, 31 Jul 2007 14:58:07 +0800")
"Huang, Ying" <ying.huang@intel.com> writes:
> On Mon, 2007-07-30 at 22:40 -0600, Eric W. Biederman wrote:
>> "Huang, Ying" <ying.huang@intel.com> writes:
>>
>> > This patch adds document for EFI x86_64 support. The boot parameters
>> > added are documented in Documentation/i386/zero-page.txt. The setup
>> > and operation guide of EFI based system is documented in
>> > Documentation/x86_64/uefi.txt.
>> >
>> > Signed-off-by: Chandramouli Narayanan <mouli@linux.intel.com>
>> > Signed-off-by: Huang Ying <ying.huang@intel.com>
>> >
>> > ---
>> >
>> > i386/zero-page.txt | 18 ++++++++++++++----
>> > x86_64/uefi.txt | 42 ++++++++++++++++++++++++++++++++++++++++++
>> > 2 files changed, 56 insertions(+), 4 deletions(-)
>> >
>> > Index: linux-2.6.23-rc1/Documentation/i386/zero-page.txt
>> > ===================================================================
>> > --- linux-2.6.23-rc1.orig/Documentation/i386/zero-page.txt 2007-07-30
>> > 11:28:45.000000000 +0800
>> > +++ linux-2.6.23-rc1/Documentation/i386/zero-page.txt 2007-07-30
>> > 11:29:28.000000000 +0800
>> > @@ -31,11 +31,11 @@
>> > 0xb0 - 0x13f Free. Add more parameters here if you really need them.
>> > 0x140- 0x1be EDID_INFO Video mode setup
>> >
>> > -0x1c4 unsigned long EFI system table pointer
>> > -0x1c8 unsigned long EFI memory descriptor size
>> > -0x1cc unsigned long EFI memory descriptor version
>> > +0x1c4 unsigned long EFI system table pointer*
>> > +0x1c8 unsigned long EFI memory descriptor size*
>> > +0x1cc unsigned long EFI memory descriptor version*
>> > 0x1d0 unsigned long EFI memory descriptor map pointer
>> > -0x1d4 unsigned long EFI memory descriptor map size
>> > +0x1d4 unsigned long EFI memory descriptor map size*
>> > 0x1e0 unsigned long ALT_MEM_K, alternative mem check, in Kb
>> > 0x1e4 unsigned long Scratch field for the kernel setup code
>> > 0x1e8 char number of entries in E820MAP (below)
>> > @@ -87,3 +87,13 @@
>> > 0x2d0 - 0xd00 E820MAP
>> > 0xd00 - 0xeff EDDBUF (edd.S) for disk signature read sector
>> > 0xd00 - 0xeeb EDDBUF (edd.S) for edd data
>> > +
>> > +Changes for x86_64 implementation:
>> > +---------------------------------
>> > +For alignment purposes, the following parameters are rearranged.
>> > +
>> > +0x1b8 unsigned long EFI system table pointer
>> > +0x1c0 unsigned long EFI Loader signature
>> > +0x1c4 unsigned long EFI memory descriptor size
>> > +0x1c8 unsigned long EFI memory descriptor version
>> > +0x1cc unsigned long EFI memory descriptor map size
>>
>> Huh? It is the same protocol. Unless there are specific issues such
>> as pointers being to small we should remain 100% the same for both
>> arch/i386 and arch/x86_64 This variation looks like a serious
>> bug.
>
> The parameters are rearranged, because the pointer is too small. For
> example, the EFI system table pointer is 8 bytes in x86_64, while it is
> 4 bytes in i386.
Ok. I see what is happening. When the documentation is for arch/i386
unsigned long is 4 bytes, and you are using unsigned long to mean 8
bytes. For an 8 byte fields please just spell out the size as 8
bytes.
How does EFI handle 32bit/64bit compatibility? In particular
how do I load a 32bit kernel on machine with a 64bit EFI? Can
it be done?
Eric
next prev parent reply other threads:[~2007-08-01 17:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 3:13 Huang, Ying
2007-07-31 4:40 ` Eric W. Biederman
2007-07-31 6:58 ` Huang, Ying
2007-08-01 17:16 ` Eric W. Biederman [this message]
2007-08-07 9:29 ` Huang, Ying
2007-08-07 9:54 ` Andi Kleen
2007-08-08 8:18 ` Huang, Ying
2007-08-08 10:08 ` Andi Kleen
2007-08-08 13:46 ` Huang, Ying
2007-08-08 14:09 ` Andi Kleen
2007-08-08 15:11 ` huang ying
2007-08-08 16:23 ` Andi Kleen
2007-08-08 16:10 ` Eric W. Biederman
2007-08-08 16:22 ` Andi Kleen
2007-08-08 17:17 ` Eric W. Biederman
2007-08-09 9:47 Etienne Lorrain
2007-08-09 10:51 ` Andi Kleen
2007-08-09 14:09 ` huang ying
2007-08-09 16:29 ` H. Peter Anvin
2007-08-09 17:01 ` Andi Kleen
2007-08-09 17:25 ` H. Peter Anvin
2007-08-10 13:03 ` Huang, Ying
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=m1r6mnnpj8.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=randy.dunlap@oracle.com \
--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
all inboxes | Powered by JetHome®