linux-kernel - Re: [PATCH 0/5] ftrace: updates for tip

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]

Date:	Thu, 22 Jan 2009 10:32:11 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/5] ftrace: updates for tip


* Steven Rostedt <rostedt@...dmis.org> wrote:

> Ingo,
> 
> These patches are fixes for the wakeup tracer.

That was quick! :-)

> The first is a fix to the empty output you reported to me earlier.
> 
> The second is a fix for the ring buffer to not record updates if it is 
> disabled, otherwised you can get empty traces there too.
> 
> The third is the wakeup change to record all tasks and not just realtime 
> tasks. It adds a wakeup_rt tracer to record only rt tasks.
> 
> The forth is the addition of the scheduling wakeup and sched switch output 
> to the wakeup tracer. This is very helpful data.
> 
> The last is probably the most important, and should go into 29 as well. I 
> never reset the timestamps used to connect the trace stamps in the 
> buffers. This can cause stale stamps to appear and explains some of the 
> really bad timestamps in the buffer I've seen.

okay, i've pulled your fixes into tip/tracing/ftrace and i've cherry-picked 
the timestamp fix over into tracing/urgent.

Thanks,

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