From: Matt Fleming <matt.fleming@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com, mjg@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64: use EFI to deal with platform wall clock
Date: Sat, 26 May 2012 11:26:48 +0100 [thread overview]
Message-ID: <1338028008.16679.1.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <4FBFBF5F020000780008637F@nat28.tlf.novell.com>
On Fri, 2012-05-25 at 16:20 +0100, Jan Beulich wrote:
> Other than ix86, x86-64 on EFI so far didn't set the {g,s}et_wallclock
> accessors to the EFI routines, thus incorrectly using raw RTC accesses
> instead.
>
> Simply removing the #ifdef around the respective code isn't enough,
> however: While so far early get-time calls were done in physical mode,
> this doesn't work properly for x86-64, as virtual addresses would still
> need to be set up for all runtime regions (which wasn't the case on the
> system I have access to), so instead the patch moves the call to
> efi_enter_virtual_mode() ahead (which in turn allows to drop all code
> related to calling efi-get-time in physical mode).
>
> Additionally the earlier calling of efi_set_executable() requires the
> CPA code to cope, i.e. during early boot it must be avoided to call
> cpa_flush_array(), as the first thing this function does is a
> BUG_ON(irqs_disabled()).
>
> Also make the two EFI functions in question here static - they're not
> being referenced elsewhere.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Matt Fleming <matt.fleming@intel.com>
> Cc: Matthew Garrett <mjg@redhat.com>
>
> ---
> (Note that due to the lack of hardware I wasn't able to test this on
> 32-bit EFI - Matt offered to do so subsequently.)
Appears to work fine here on 32-bit.
next prev parent reply other threads:[~2012-05-26 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 15:20 Jan Beulich
2012-05-25 15:24 ` Matthew Garrett
2012-05-25 15:30 ` Jan Beulich
2012-05-25 15:34 ` Matthew Garrett
2012-06-06 9:47 ` Ingo Molnar
2012-05-26 10:26 ` Matt Fleming [this message]
2012-06-04 8:11 ` Jan Beulich
2012-06-06 15:16 ` [tip:x86/efi] x86-64/efi: Use " tip-bot for Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2012-05-15 12:18 [PATCH] x86-64: use " Jan Beulich
2012-05-15 12:47 ` Matthew Garrett
2012-05-15 13:19 ` Jan Beulich
2012-05-15 13:20 ` Matthew Garrett
2012-05-16 12:18 ` Jan Beulich
2012-05-16 12:39 ` Matthew Garrett
2012-05-16 12:59 ` Jan Beulich
2012-05-16 13:07 ` Matthew Garrett
2012-05-17 8:31 ` Matt Fleming
2012-05-25 15:00 ` Jan Beulich
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=1338028008.16679.1.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=tglx@linutronix.de \
/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®