linux-kernel - Re: [Patch -tip 3/3] Tracing/ftrace: Don't consume entries unhandled by mmiotrace

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]

Message-ID: <alpine.DEB.1.10.0809271420210.11231@gandalf.stny.rr.com>
Date:	Sat, 27 Sep 2008 14:25:20 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Frédéric Weisbecker <fweisbec@...il.com>,
	Pekka Paalanen <pq@....fi>, linux-kernel@...r.kernel.org
Subject: Re: [Patch -tip 3/3] Tracing/ftrace: Don't consume entries unhandled
 by mmiotrace

On Sat, 27 Sep 2008, Ingo Molnar wrote:
> 
> the new trace-ringbuffer design Steve is working on would abstract away 
> this complication - then we could make tracers truly independent 
> entities.

Yep, I even started implementing this. What is nice about this too, is 
that we could even mix the tracer buffers together in the merge sort. 
Since all buffers use the same timestamping, we can keep the separate 
buffers out, turn on different tracers, and have the output show them all 
together.

This would mean that we can keep the function tracer buffer large, and the 
other tracer buffers smaller. And merge them together when needed.

I'll have to recreate it, since the buffer code changed quite a bit since 
I first started making ftrace do this. Also, I want to make the changes to 
ftrace as incremental as possible. That way we could easily diagnose 
problems that arise.

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