From: "Huang, Ying" <ying.huang@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.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: Tue, 07 Aug 2007 17:29:44 +0800 [thread overview]
Message-ID: <1186478984.3769.46.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <m1r6mnnpj8.fsf@ebiederm.dsl.xmission.com>
On Thu, 2007-08-02 at 01:16 +0800, Eric W. Biederman wrote:
> > 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.
Ok. Will do in the next version.
>
> 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?
>
Because the EFI memory map is converted to E820 map in bootloader now,
it is possible to load 32bit kernel on machine with a 64bit EFI. But it
is almost impossible to call EFI runtime service in 32bit kernel. But I
think EFI runtime service is not essential in this situation, because
the raw hardware can be used too.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2007-08-07 9:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 3:13 [PATCH 5/5] x86_64 EFI support -v3: EFI document 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
2007-08-07 9:29 ` Huang, Ying [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=1186478984.3769.46.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=randy.dunlap@oracle.com \
--cc=yhlu.kernel@gmail.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.