linux-kernel - Re: [PATCH] tracing/ftrace: use preempt_enable_no_resched_notrace in ring_buffer_time

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:	Tue, 16 Dec 2008 17:53:13 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Frédéric Weisbecker <fweisbec@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/ftrace: use preempt_enable_no_resched_notrace
 in ring_buffer_time_stamp()


On Tue, 16 Dec 2008, Ingo Molnar wrote:
> 
> i noticed high stack-tracer overhead too. Which is understandable i guess: 
> the stack tracer keeps the mcount callbacks running all the time and can 
> save the stack backtrace of the highest-stack-usage point in time that the 
> kernel ever has hit in the past. That is a pretty powerful debug 
> capability, with appropriate costs.

I was thinking of having a way to start and stop the stack tracer. This 
way we can actually have it on by default with anything that has dynamic 
ftace. To enable it durning boot would require a kernel command line 
option. Other than that, I would have a sysctl enable it.

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