[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1186478984.3769.46.camel@caritas-dev.intel.com>
Date: Tue, 07 Aug 2007 17:29:44 +0800
From: "Huang, Ying" <ying.huang@...el.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: ak@...e.de, akpm@...ux-foundation.org,
Yinghai Lu <yhlu.kernel@...il.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
Chandramouli Narayanan <mouli@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists