] [odp-lng] [Patch v3 1/3] api: time: unbind CPU
cycles from time API
Petri,
On 03.09.15 16:13, Ivan Khoronzhuk wrote:
On 03.09.15 15:29, Savolainen, Petri (Nokia - FI/Espoo) wrote:
There are many example apps that actually want to measure execution
time in CPU cycles, not in nsec.
Time API
> -Original Message-
> From: ext Ivan Khoronzhuk [mailto:ivan.khoronz...@linaro.org]
> Sent: Thursday, September 03, 2015 6:26 PM
> To: Savolainen, Petri (Nokia - FI/Espoo); lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [odp-lng] [Patch v3 1/3] api: time: unbind CP
ice.
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of
ext Ivan Khoronzhuk
Sent: Thursday, September 03, 2015 12:11 AM
To: lng-odp@lists.linaro.org
Subject: [lng-odp] [odp-lng] [Patch v3 1/3] api: time: unbind CPU
cycles from time API
Current time AP
.
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of
ext Ivan Khoronzhuk
Sent: Thursday, September 03, 2015 12:11 AM
To: lng-odp@lists.linaro.org
Subject: [lng-odp] [odp-lng] [Patch v3 1/3] api: time: unbind CPU
cycles from time API
Current time API
actual time API
use cases.
> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of
> ext Ivan Khoronzhuk
> Sent: Thursday, September 03, 2015 12:11 AM
> To: lng-odp@lists.linaro.org
> Subject: [lng-odp] [odp-lng] [Patch v3 1/3] api
Current time API supposes that frequency of counter is equal
to CPU frequency. But that's not always true, for instance,
in case if no access to CPU cycle counter, another hi-resolution
timer can be used, and it`s rate can be different from CPU
rate. There is no big difference in which cycles to me
