linux-kernel - Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

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: <20060919122933.GA11337@infradead.org>
Date:	Tue, 19 Sep 2006 13:29:33 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	"Frank Ch. Eigler" <fche@...hat.com>, karim@...rsys.com,
	Tim Bird <tim.bird@...sony.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...l.org>, Ingo Molnar <mingo@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tom Zanussi <zanussi@...ibm.com>, ltt-dev@...fik.org,
	Michel Dagenais <michel.dagenais@...ymtl.ca>
Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

On Fri, Sep 15, 2006 at 09:10:44PM +0200, Roman Zippel wrote:
> Hi,
> 
> On Fri, 15 Sep 2006, Ingo Molnar wrote:
> 
> > > Ar Gwe, 2006-09-15 am 13:08 -0400, ysgrifennodd Frank Ch. Eigler:
> > > > Alan Cox <alan@...rguk.ukuu.org.uk> writes:
> > > > - where 1000-cycle int3-dispatching overheads too high
> > > 
> > > Why are your despatching overheads 1000 cycles ? (and if its due to 
> > > int3 why are you using int 3 8))
> > 
> > this is being worked on actively: there's the "djprobes" patchset, which 
> > includes a simplified disassembler to analyze common target code and can 
> > thus insert much faster, call-a-trampoline-function based tracepoints 
> > that are just as fast as (or faster than) compile-time, static 
> > tracepoints.
> 
> Who is going to implement this for every arch?
> Is this now the official party line that only archs, which implement all 
> of this, can make use of efficient tracing?

Come on, stop trying to be an asshole.  It's always been the case that to
use new functionality you have to add arch code where nessecary.
-
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/