From: Shuah Khan <shuahkh@osg.samsung.com>
To: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH] kselftest/timers: Set default threadtest values to simplify execution scripts
Date: Thu, 19 Mar 2015 16:01:58 -0600 [thread overview]
Message-ID: <550B4756.2040208@osg.samsung.com> (raw)
In-Reply-To: <1426693913-5738-1-git-send-email-john.stultz@linaro.org>
On 03/18/2015 09:51 AM, John Stultz wrote:
> In order to keep the kselftest Makefiles simpler, set the threadtest
> default values to the ones used in standard run_tests
>
> Cc: Shuah Khan <shuahkh@osg.samsung.com>
> Cc: Prarit Bhargava <prarit@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Richard Cochran <richardcochran@gmail.com>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> ---
> tools/testing/selftests/timers/threadtest.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
Applied to next for 4.1
Some numbers for you with timer tests included:
make kselftest target takes:
real 11m50.499s
user 3m25.979s
sys 5m45.433s
It is creeping up, previous timing was
real 9.41
user 3.55
system 0:24.86
Not concerned yet. Might be getting closer to
needing to defining quick vs long test categories.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-03-19 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 15:51 [PATCH] kselftest/timers: Set default threadtest values to simplify execution scripts John Stultz
2015-03-19 22:01 ` Shuah Khan [this message]
2015-03-19 22:34 ` John Stultz
2015-03-19 22:48 ` Shuah Khan
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=550B4756.2040208@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.