linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: joeyli <jlee-IBi9RG/b67k@public.gmane.org>
Cc: Matthew Garrett
	<matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>,
	"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] UEFI: Don't use UEFI time services on 32-bit
Date: Tue, 10 Dec 2013 20:00:01 -0800	[thread overview]
Message-ID: <52A7E341.6050509@zytor.com> (raw)
In-Reply-To: <1386721257.3539.1717.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>

On 12/10/2013 04:20 PM, joeyli wrote:
> 
> Actually, I am working on the timezone support of ACPI TIME and EFI
> TIME. My current implementation is using EFI time services to deal with
> clock in RTC.
> 
> The ACPI TAD is a generic device that need parse DSDT for access it. The
> DSDT parser is in subsystem initial stage. But in start_kernel, the
> timekeeping_init() call wallclock functions to deal system clock with
> RTC, it's too early for access ACPI TAD, so it still access CMOS
> interface unless switch it to EFI services.
> 
> If we adapt to ACPI TAD, then how does system clock deal with RTC
> through it when system boot?
> 

I don't really have a good answer for that.  We could call the EFI
services from the boot stub, of course, and pass in an approximate time
(and perhaps the TSC value to go with it), but I'm not sure if that will
be adequate.

The other alternative would be to either parse ACPI earlier or
initialize wall time later.

	-hpa

      parent reply	other threads:[~2013-12-11  4:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 19:44 [PATCH] UEFI: Don't use UEFI time services on 32-bit Matthew Garrett
     [not found] ` <1385754283-2464-1-git-send-email-matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
2013-11-29 22:04   ` joeyli
     [not found]     ` <1385762647.3539.4.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-11-29 22:30       ` Borislav Petkov
2013-12-05 10:56       ` Matt Fleming
2013-11-30  1:45   ` H. Peter Anvin
     [not found]     ` <52994324.4000404-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-12-10 22:54       ` H. Peter Anvin
     [not found]         ` <52A79B9A.7080004-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-12-10 22:58           ` Matthew Garrett
2013-12-10 23:20             ` H. Peter Anvin
     [not found]               ` <52A7A1B0.7050903-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-12-10 23:24                 ` Matthew Garrett
2013-12-10 23:51                   ` H. Peter Anvin
     [not found]                     ` <52A7A915.1070701-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-12-11  0:20                       ` joeyli
     [not found]                         ` <1386721257.3539.1717.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-12-11  4:00                           ` H. Peter Anvin [this message]

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=52A7E341.6050509@zytor.com \
    --to=hpa-ymnouzjc4hwavxtiumwx3w@public.gmane.org \
    --cc=jlee-IBi9RG/b67k@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).