From: Andrew Lunn <andrew@lunn.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Lukasz Majewski <l.majewski@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Thomas Abraham <ta.omasab@gmail.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Lukasz Majewski <l.majewski@majess.pl>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"thomas.ab@samsung.com" <thomas.ab@samsung.com>,
Sachin Kamat <spk.linux@gmail.com>,
Tomasz Figa <t.figa@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
Date: Wed, 23 Jul 2014 17:02:28 +0200 [thread overview]
Message-ID: <20140723150228.GE2856@lunn.ch> (raw)
In-Reply-To: <CAKohpok++gPcNk9-E4MsFdNBy8qL7oLYvatk1EvcW1OHwroZXQ@mail.gmail.com>
On Wed, Jul 23, 2014 at 02:19:54PM +0530, Viresh Kumar wrote:
> On 23 July 2014 13:08, Lukasz Majewski <l.majewski@samsung.com> wrote:
> > Do you want to say that we have enough tests and we don't need more ?
>
> No. We don't have any tests at all :)
Not really true. I've found bugs triggering opps using cpufreq-bench.
http://marc.info/?l=linux-pm&m=138165517321579&w=2
and i hope you learned from that experience and run this tool when
making changes to the core.
There is an old writeup of cpufreq-bench here:
https://lwn.net/Articles/339862/
and the code itself is in the mainline tree, tools/power/cpupower/bench
Andrew
next prev parent reply other threads:[~2014-07-23 15:02 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
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 [this message]
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=20140723150228.GE2856@lunn.ch \
--to=andrew@lunn.ch \
--cc=cpufreq@vger.kernel.org \
--cc=l.majewski@majess.pl \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=spk.linux@gmail.com \
--cc=t.figa@samsung.com \
--cc=ta.omasab@gmail.com \
--cc=thomas.ab@samsung.com \
--cc=viresh.kumar@linaro.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