public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tian, Feng" <feng.tian@intel.com>
To: Arka Sharma <arka.sw1988@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Tian, Feng" <feng.tian@intel.com>
Subject: Re: NvmExpressDxe TimerEvent frequency
Date: Mon, 10 Apr 2017 04:39:21 +0000	[thread overview]
Message-ID: <7F1BAD85ADEA444D97065A60D2E97EE5699E343C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPO=kN1W0=RecG1R9a6jh+-qhvHeGTuc2r_oo+V0+Rt+BLm_xA@mail.gmail.com>

Yes.

For example, old platforms usually use 50ms as timer interval. So at such platforms, even the code is programming to use 1 ms timer, the actual trigger time interval is 50ms.

Thanks
Feng

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Arka Sharma
Sent: Sunday, April 9, 2017 12:41 PM
To: edk2-devel@lists.01.org
Subject: [edk2] NvmExpressDxe TimerEvent frequency

Hi,

UEFI Driver Write Guide section 5.1.6 says "UEFI system firmware uses a hardware timer interrupt to measure time.
These. These
time measurements are used to determine when enough time has passed to signal a timer event programmed with SetTimer(). In most systems, the timer interrupt is generated every 10 ms to 50 ms, but the UEFI Specification does not require any specific interrupt rate. This lack of specificity means that a periodic timer programmed with a period much smaller than 10 ms may only be signaled every 10 ms to 50 ms.". So in case of NvmExpressDxe the Private->TimerEvent is set with 1 ms, so the frequency of the routine ProcessAsyncTaskList might be more than 1 ms as per the frequency of the timer interrupt ?

Regards,
Arka
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-04-10  4:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-09  4:41 NvmExpressDxe TimerEvent frequency Arka Sharma
2017-04-10  4:39 ` Tian, Feng [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=7F1BAD85ADEA444D97065A60D2E97EE5699E343C@SHSMSX101.ccr.corp.intel.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