From: Shuah Khan <shuahkh@osg.samsung.com>
To: Namhyung Kim <namhyung@kernel.org>, Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Pádraig Brady" <P@draigBrady.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Dave Jones" <davej@codemonkey.org.uk>,
"Luis Henriques" <luis.henriques@canonical.com>,
"Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
"Shuah Khan" <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v3] ftracetest: Do not use usleep directly
Date: Fri, 03 Apr 2015 09:26:16 -0600 [thread overview]
Message-ID: <551EB118.201@osg.samsung.com> (raw)
In-Reply-To: <1428020878-28690-1-git-send-email-namhyung@kernel.org>
On 04/02/2015 06:27 PM, Namhyung Kim wrote:
> The usleep is only provided on distros from Redhat so running ftracetest
> on other distro resulted in failures due to the missing usleep.
>
> The reason of using [u]sleep in the test was to generate (scheduler)
> events. It can be done various ways like this:
>
> yield() { ping localhost -c 1 || sleep .001 || usleep 1 || sleep 1; }
>
> For more information to the history of this patch, please refer to:
>
> Link: http://lkml.kernel.org/r/1427329943-16896-1-git-send-email-namhyung@kernel.org
>
> Reported-by: Michael Ellerman <mpe@ellerman.id.au>
> Reported-by: Dave Jones <davej@codemonkey.org.uk>
> Reported-by: Luis Henriques <luis.henriques@canonical.com>
> Suggested-by: Pádraig Brady <P@draigBrady.com>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
Thanks for getting to this quickly. Applied it to
linux-kselftest next for 4.1
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
prev parent reply other threads:[~2015-04-03 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 0:27 [PATCH v3] ftracetest: Do not use usleep directly Namhyung Kim
2015-04-03 15:26 ` Shuah Khan [this message]
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=551EB118.201@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=P@draigBrady.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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