All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
To: "hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org"
	<hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: "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 23:24:23 +0000	[thread overview]
Message-ID: <1386717862.26245.5.camel@x230> (raw)
In-Reply-To: <52A7A1B0.7050903-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>

On Tue, 2013-12-10 at 15:20 -0800, H. Peter Anvin wrote:
> On 12/10/2013 02:58 PM, Matthew Garrett wrote:
> > EFI is preferable to PNP in that it gives us a timezone, and Windows
> > certainly calls the EFI time functions. *However*, it doesn't appear to
> > do so once the system is booted. So we probably want to call it in the
> > boot stub and find some way to pass the timezone information up to the
> > kernel, and then spend some more time instrumenting Windows to figure
> > out how it makes time calls.
> 
> TAD would also give us the timezone.  I'm not sure how you can
> realistically only use the time function during boot, however, unless
> you inherently assume it is coherent with the hardware RTC, since you
> wouldn't be able to set it.

If we can verify that Windows actually uses TAD then I'd agree it's
preferable to EFI, but if we can't then I wouldn't be so sure. I'll redo
my Windows instrumentation and figure out under which circumstances it's
calling the time functions.

-- 
Matthew Garrett <matthew.garrett@nebula.com>

  parent reply	other threads:[~2013-12-10 23:24 UTC|newest]

Thread overview: 13+ 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 [this message]
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
2013-12-10 23:22 ` [tip:x86/urgent] x86, efi: Don't use (U) EFI time services on 32 bit tip-bot for Matthew Garrett

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=1386717862.26245.5.camel@x230 \
    --to=matthew.garrett-05xso3yj/jvqt0dzr+alfa@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.