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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080927174756.GF26047@elte.hu>
Date:	Sat, 27 Sep 2008 19:47:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frédéric Weisbecker <fweisbec@...il.com>
Cc:	Pekka Paalanen <pq@....fi>, linux-kernel@...r.kernel.org,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [Patch -tip 3/3] Tracing/ftrace: Don't consume entries
	unhandled by mmiotrace


* Frédéric Weisbecker <fweisbec@...il.com> wrote:

> 2008/9/25 Pekka Paalanen <pq@....fi>:
> > We can (must) return to this if/when multiple tracers are allowed
> > to be active simultaneously. But in the current situation, I do not
> > see a way to trace more than one thing, but I haven't really looked
> > into the other tracers.
> 
> You can enable another tracer simultaneously. I never tried it but you 
> can launch one from debugfs and another from kernel code for example. 
> The new boot tracer will have to launch the sched_switch tracer.

hm, right now i can see a lot of problems with that approach - the 
buffers are partly per tracer and partly global.

the new trace-ringbuffer design Steve is working on would abstract away 
this complication - then we could make tracers truly independent 
entities.

	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/