[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708071154.23150.ak@suse.de>
Date: Tue, 7 Aug 2007 11:54:22 +0200
From: Andi Kleen <ak@...e.de>
To: "Huang, Ying" <ying.huang@...el.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
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 Tuesday 07 August 2007 11:29:44 Huang, Ying wrote:
> > 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.
The 32bit EFI code doesn't know this yet, does it?
> 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.
That doesn't sound good. Is this really supposed to work this way?
If the raw hardware works why are we using EFI services at all?
We generally trust hardware more than BIOSes.
Might we end up with machines that only boot with the 64bit kernel?
Will systems have a dual EFI implementation?
Also long term I would like to use a few useful EFI services,
like the support to put some data into the CMOS area to survive
a reboot. That would be quite useful for panics and oopses.
But we would prefer to have that on 32bit too.
-Andi
-
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