From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=63.128.21.170; helo=us-smtp-delivery-170.mimecast.com; envelope-from=ken_taylor@phoenix.com; receiver=edk2-devel@lists.01.org Received: from us-smtp-delivery-170.mimecast.com (us-smtp-delivery-170.mimecast.com [63.128.21.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id CC0D92034A7AA for ; Mon, 23 Oct 2017 17:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=phoenix.com; s=mimecast20170203; t=1508806386; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=4NiutSqtrztXqiR121L06p4opIeTlIpDVTmE/Ag95t8=; b=hLypwWKLhjfvGRdfSP0JIGvEV+wM1itFbYM/4miP4W/yzr8gQ+yoybOO9pbFZLRFWVz4i6qw7f77KPuuOw7kePMpR3QMtulK3JfQLiKb+fmMM+Tn3l8Vz3zZu4dpocUOoPqjkbOq5uUc1WLmrFlqkMnEkNxy7u80adP0akLywhg= X-CrossPremisesHeadersFilteredBySendConnector: SCL-EXCHMB-13.phoenix.com Received: from SCL-EXCHMB-13.phoenix.com (scl-owa.phoenix.com [134.122.240.15]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-208-oGwuUKFIO6GFazr5AHAqLQ-1; Mon, 23 Oct 2017 20:53:04 -0400 Received: from SCL-EXCHMB-13.phoenix.com (2607:f0dc:5001:1:f438:5eb8:75e6:cad4) by SCL-EXCHMB-13.phoenix.com (2607:f0dc:5001:1:f438:5eb8:75e6:cad4) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Mon, 23 Oct 2017 17:53:01 -0700 Received: from SCL-EXCHMB-13.phoenix.com ([fe80::fd2e:a8f8:f740:cb3b]) by SCL-EXCHMB-13.phoenix.com ([fe80::fd2e:a8f8:f740:cb3b%12]) with mapi id 15.00.1156.000; Mon, 23 Oct 2017 17:53:01 -0700 From: Ken Taylor To: David F. , edk2 developers list Thread-Topic: [edk2] Fwd: timer ticks ? Thread-Index: AQHTTFrz0b1BoHdmLU215/R/uJOzMaLyKKcA Date: Tue, 24 Oct 2017 00:53:01 +0000 Message-ID: <1ff86daafb794c2783c934eeda2b85c8@SCL-EXCHMB-13.phoenix.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [134.122.40.54] MIME-Version: 1.0 X-OrganizationHeadersPreserved: SCL-EXCHMB-13.phoenix.com X-MC-Unique: oGwuUKFIO6GFazr5AHAqLQ-1 Subject: Re: timer ticks ? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 00:49:25 -0000 Content-Language: en-US Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable 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 Davi= d 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 applic= ation 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 oth= er 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