lkml.org 
[lkml]   [2010]   [Aug]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: EFI runtime-services on x86_64
From
Date
Huang Ying <ying.huang@intel.com> writes:

> Hi, Bjorn,
>
> On Mon, 2010-08-02 at 10:35 +0800, Tang, Feng wrote:
>> Hi Bjorn,
>>
>> On Sat, 31 Jul 2010 04:58:48 +0800
>> Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>>
>> > Hello Feng,
>> >
>> > Can you educate me about your commit 772be899bc, "86: Make EFI RTC
>> > function depend on 32bit again"?
>> >
>> > It adds "#ifdef CONFIG_X86_32" to avoid using efi_get_time() and
>> > efi_set_rtc_mmss(), but there's no explanation of *why* those services
>> > only work on 32-bit.
>> >
>> > Is this an EFI spec limitation? Do the other EFI runtime services
>> > work on 64-bit, since you didn't touch them? Or do we just not use
>> > any of the others?
>> >
>>
>> Commit 772be899bc, "86: Make EFI RTC function depend on 32bit again" is
>> a regression fix for 7bd867d "x86: Move get/set_wallclock to x86_platform_ops".
>> These 2 commits just abstract the rtc service for legacy x86 PC/EFI/Virtualiation
>> kernel, and has no functional change to existing code.
>>
>> I'm not familiar with EFI, but my understanding is current EFI code in
>> kernel only provides the get/set_time service for x86_32 platform.
>
> I think get/set_time service should have worked on x86_64 too. Just
> lacks proper debugging/testing for recent kernels.

Is there any reason we just don't rip those calls out?

If we don't need them and we lack proper debug/testing I don't see the point
of using the EFI calls and exposing ourselves to more potential BIOS breakage.

EFI runtime calls have the nasty fact that they don't work in general even
if EFI is present because you may have the wrong word size EFI running on
your machine. A 32bit EFI and a 64bit kernel or a 64bit EFI and a 32bit kernel.

Eric


\
 
 \ /
  Last update: 2010-08-03 23:49    [from the cache]
©2003-2011 Jasper Spaans