public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ken Taylor <Ken_Taylor@phoenix.com>
To: David F. <df7729@gmail.com>,
	edk2 developers list <edk2-devel@lists.01.org>
Subject: Re: timer ticks ?
Date: Tue, 24 Oct 2017 00:53:01 +0000	[thread overview]
Message-ID: <1ff86daafb794c2783c934eeda2b85c8@SCL-EXCHMB-13.phoenix.com> (raw)
In-Reply-To: <CAGRSmLu37=omHuz3GK_NY0e90U1k3TMoGjYjQz78pm9L3+TW+w@mail.gmail.com>

Hi David,

I think EVT_TIMER is required functionality.  Many drivers depend on it.

I know it goes away at runtime, but so do the rest of boot services.  There's nothing that can be done about that; even the BIOS timer tick was taken over by all modern operating systems, so it wasn't reliably persistent post boot either.

Regards,
-Ken.

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of David F.
Sent: Monday, October 23, 2017 4:59 PM
To: edk2 developers list
Subject: [edk2] Fwd: timer ticks ?

Hi,

Is there a reliable (always available) way to get a timer tick in an application similar to the old 18.2 per second timer tick from BIOS.
That one was always there, high speed access (no slow access to a RTC)  and the tick count is known (to approx calculate intervals for polling and other things).  In UEFI,  EVT_TIMER may not be supported.
GetTime may be slow RTC access.    It can be a counter only since
machine was on.

TIA!
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel



      reply	other threads:[~2017-10-24  0:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGRSmLv1NoKDKu1cJ_g=D7buPSF+9McB6Pts9D5FaMg=nhAp5A@mail.gmail.com>
2017-10-23 23:59 ` timer ticks ? David F.
2017-10-24  0:53   ` Ken Taylor [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-list 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=1ff86daafb794c2783c934eeda2b85c8@SCL-EXCHMB-13.phoenix.com \
    --to=devel@edk2.groups.io \
    /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