On 04/21/16 11:18, Savolainen, Petri (Nokia - FI/Espoo) wrote:
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of EXT
Maxim Uvarov
Sent: Wednesday, April 20, 2016 7:04 PM
To: lng-odp@lists.linaro.org
Subject: Re: [lng-odp] [PATCH] validation: time
> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of EXT
> Maxim Uvarov
> Sent: Wednesday, April 20, 2016 7:04 PM
> To: lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
>
>
that patch is not part of current series, please skip it. Other 2
paches are good for review.
Maxim.
On 04/20/16 19:02, Maxim Uvarov wrote:
From: Petri Savolainen
Time test duration was almost a minute on a 2.6GHz CPU.
Combined local and global time monotonity
From: Petri Savolainen
Time test duration was almost a minute on a 2.6GHz CPU.
Combined local and global time monotonity tests, so that
the there is only single run of the long wait loop.
Shortened wait test time to 3 seconds and long loop into
roughly 14 seconds on a
> -Original Message-
> From: EXT Ivan Khoronzhuk [mailto:ivan.khoronz...@linaro.org]
> Sent: Monday, April 18, 2016 3:53 PM
> To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com>;
> lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [PATCH] valida
Hi, Petri
Tests are sorted in the order of API usage, one by one. The monotony test is
placed before others,
because before testing rest time APIs we should be sure in monotony. Now when
you've combined them
the placement of monotony at least for one of the type is not correct. For
instance,
EXT Ivan Khoronzhuk [mailto:ivan.khoronz...@linaro.org]
Sent: Thursday, April 14, 2016 5:39 PM
To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com>;
lng-odp@lists.linaro.org
Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
What about to do smth like below
lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
>
> What about to do smth like below
> (I didn't normalize it to ns...but that are tehnical details)
>
> uint64_t c1, c2;
> uint64_t loop_time;
>
> c1 =
onzhuk [mailto:ivan.khoronz...@linaro.org]
Sent: Thursday, April 14, 2016 5:00 PM
To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com>;
lng-odp@lists.linaro.org
Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
Hi, Petri.
As far I remember you was OK to i
;
lng-odp@lists.linaro.org
Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
Hi, Petri.
As far I remember you was OK to increase time of testing on even more
time.
It was supposed to include future freqs...I know, for now it's not
correct..
but anyway. Also I dislike the idea t
ay, April 14, 2016 5:00 PM
> To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com>;
> lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [PATCH] validation: time: shorten test duration
>
> Hi, Petri.
>
> As far I remember you was OK to increase time of testing
Hi, Petri.
As far I remember you was OK to increase time of testing on even more time.
It was supposed to include future freqs...I know, for now it's not correct..
but anyway. Also I dislike the idea to combine two separate tests in one
function.
Yes, it makes tests faster, but doesn't reflect
Time test duration was almost a minute on a 2.6GHz CPU.
Combined local and global time monotonity tests, so that
the there is only single run of the long wait loop.
Shortened wait test time to 3 seconds and long loop into
roughly 14 seconds on a 2.6GHz CPU. There should be enough
head room to keep
13 matches
Mail list logo