linux-kernel - Re: [PATCH] ftracetest: Replace usleep with sleep 0.000001

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141223042118.GD14960@sejong>
Date:	Tue, 23 Dec 2014 13:21:18 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Pavel Machek <pavel@....cz>, Michael Ellerman <mpe@...erman.id.au>,
	masami.hiramatsu.pt@...achi.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ftracetest: Replace usleep with sleep 0.000001

On Sat, Dec 20, 2014 at 05:07:25PM -0500, Steven Rostedt wrote:
> On Sat, 20 Dec 2014 21:42:13 +0100
> Pavel Machek <pavel@....cz> wrote:
> 
> > On Wed 2014-12-10 15:38:27, Michael Ellerman wrote:
> > > usleep is a Fedoraism, it's not generally available on Debian based
> > > systems AFAICS.
> > > 
> > > GNU sleep accepts a floating point argument, so use that instead.
> > > 
> > > Signed-off-by: Michael Ellerman <mpe@...erman.id.au>
> > 
> > Could ftrace user interface be enhanced not to need random delays?
> > 
> 
> Not sure what you are talking about. These "random delays" are not for
> the interface, but instead to force some events to happen and to make
> sure they did.
> 
> As the subject states, this is for "ftracetest" which is the selftests
> for ftrace.
> 
> The usleep is basically a "do something to trigger events", and we
> don't want to wait long in doing it.

Right.  AFAIK what ftracetest expects is a scheduler event so it
doesn't need to be the [u]sleep.

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/