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] [day] [month] [year] [list]
Date:	Wed, 4 May 2016 15:49:06 +0200 (CEST)
From:	John Kacur <jkacur@...hat.com>
To:	Luiz Capitulino <lcapitulino@...hat.com>
cc:	Clark Williams <williams@...hat.com>,
	RT <linux-rt-users@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cyclictest: stop any tracing after hitting a breaktrace
 threshold



On Wed, 4 May 2016, Luiz Capitulino wrote:

> On Tue, 3 May 2016 15:28:39 -0500
> Clark Williams <williams@...hat.com> wrote:
> 
> > The intent is to be able to do something like this:
> > 
> >     trace-cmd start -e all -p function
> >     rteval --duration=12h --cyclictest-breaktrace=150
> >     trace-cmd extract
> 
> Ah, ok, I get it now. This makes sense.
> 
> I think I'd refactor the code opening tracing_on to its own
> function so that we avoid the duplicate code in setup_tracer(),
> but in any case:
> 
> Reviewed-by: Luiz Capitulino <lcapitulino@...hat.com>
> --

Sorry, resending with a sane mailer

I don't see a better solution for now, so
adding Luiz Reviewed by
Signed-off-by: John Kacur <jkacur@...hat.com>

and pushed to devel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ