From: spk.linux@gmail.com (Sachin Kamat)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: tests: Providing cpufreq regression test
Date: Tue, 22 Jul 2014 09:43:45 +0530 [thread overview]
Message-ID: <CAK5sBcGdrmfkc_hyV3DewwLjGa3=1xjctzqcTNC9C2yPFmEFCg@mail.gmail.com> (raw)
In-Reply-To: <20140718135933.0837e094@amdc2363>
Hi Lukasz,
On Fri, Jul 18, 2014 at 5:29 PM, Lukasz Majewski <l.majewski@samsung.com> wrote:
> Hi Sachin,
>
>> Hi Lukasz,
>>
>> I tested this script on 4210 based Origen board.
>> This is the output:
>> ./cpufreq_freq_test.sh
>> CURRENT GOVERNOR: performance
>> SET GOVERNOR: performance
>> ######################################
>> TEST AVAILABLE FREQS
>> ######################################
>> FREQ: 1200000 sleep: invalid number '0.1'
>> [ 5.918347] random: gzip urandom read with 61 bits of entropy
>> available OK
>> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> ######################################
>> TEST FREQS SWITCHING
>> ######################################
>> REFERENCE FREQ: 1200000
>> FREQ: 1200000 ----> FREQ: 1200000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1200000 ----> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1200000 ----> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1200000 ----> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1200000 ----> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> REFERENCE FREQ: 1000000
>> FREQ: 1000000 ----> FREQ: 1200000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1000000 ----> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1000000 ----> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1000000 ----> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 1000000 ----> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> REFERENCE FREQ: 800000
>> FREQ: 800000 ----> FREQ: 1200000 sleep: invalid number '0.1'
>> OK
>> FREQ: 800000 ----> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 800000 ----> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 800000 ----> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 800000 ----> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> REFERENCE FREQ: 500000
>> FREQ: 500000 ----> FREQ: 1200000 sleep: invalid number '0.1'
>> OK
>> FREQ: 500000 ----> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 500000 ----> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 500000 ----> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 500000 ----> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> REFERENCE FREQ: 200000
>> FREQ: 200000 ----> FREQ: 1200000 sleep: invalid number '0.1'
>> OK
>> FREQ: 200000 ----> FREQ: 1000000 sleep: invalid number '0.1'
>> OK
>> FREQ: 200000 ----> FREQ: 800000 sleep: invalid number '0.1'
>> OK
>> FREQ: 200000 ----> FREQ: 500000 sleep: invalid number '0.1'
>> OK
>> FREQ: 200000 ----> FREQ: 200000 sleep: invalid number '0.1'
>> OK
>> ######################################
>> ERRORS: 0
>> ######################################
>>
>> Though it says 0 errors, what does the "invalid number..." signify?
>
> I guess that this message is caused by your default sleep
> implementation.
>
> Could you type 'sleep 0.1' and then 'sleep 1' in your console on the
> target system?
> Is the "invalid number" not present with the second case?
Only with first case (sleep 0.1) I get the "invalid number" message.
sleep 1 seems to be OK.
--
Regards,
Sachin.
next prev parent reply other threads:[~2014-07-22 4:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:23 [PATCH] cpufreq: tests: Providing cpufreq regression test Lukasz Majewski
2014-07-18 11:28 ` Sachin Kamat
2014-07-18 11:59 ` Lukasz Majewski
2014-07-22 4:13 ` Sachin Kamat [this message]
2014-07-18 11:42 ` Rafael J. Wysocki
2014-07-18 12:00 ` Lukasz Majewski
2014-07-21 7:02 ` [PATCH v2] " Lukasz Majewski
2014-07-23 5:06 ` Viresh Kumar
2014-07-23 7:38 ` Lukasz Majewski
2014-07-23 8:49 ` Viresh Kumar
2014-07-23 10:10 ` Lukasz Majewski
2014-07-23 10:48 ` Viresh Kumar
2014-07-24 10:05 ` Javi Merino
2014-07-23 11:58 ` Rafael J. Wysocki
2014-07-23 15:02 ` Andrew Lunn
2014-07-23 23:58 ` Rafael J. Wysocki
2014-07-24 7:04 ` Lukasz Majewski
2014-08-06 22:50 ` Rafael J. Wysocki
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-all 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='CAK5sBcGdrmfkc_hyV3DewwLjGa3=1xjctzqcTNC9C2yPFmEFCg@mail.gmail.com' \
--to=spk.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).