linux-kernel - Re: [PATCH 02/10] ftrace: fix boot trace sched startup

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:	Sat, 8 Nov 2008 07:17:22 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frédéric Weisbecker <fweisbec@...il.com>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 02/10] ftrace: fix boot trace sched startup


On Sat, 8 Nov 2008, Fr?d?ric Weisbecker wrote:
> 
> BTW: I see that tracing_reset is called even on start and reset
> callback by the tracers. Wouldn't it better to do it
> only on reset? Perhaps it can even be done automatically by the
> tracing Api itself when reset is called on
> every tracers. Or perhaps there could be special cases I don't see
> where one tracer wouldn't wish to erase is entries
> on reset?

I'm maintaining the original behaviour. We can discusss whether or
not the start should also reset. I'm up for different ideas.

> 
> Acked-by: Frederic Weisbecker <fweisbec@...il.com>

Thanks,

-- Steve

--
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/