linux-kernel - Re: [PATCH 0/2] A kernel tracing interface

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: <46F02CF5.3060902@us.ibm.com>
Date:	Tue, 18 Sep 2007 12:54:29 -0700
From:	David Wilder <dwilder@...ibm.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Vara Prasad <prasadav@...ibm.com>,
	linux-kernel@...r.kernel.org,
	SystemTAP <systemtap@...rces.redhat.com>
Subject: Re: [PATCH 0/2] A kernel tracing interface

Mathieu Desnoyers wrote:
> * Andrew Morton (akpm@...ux-foundation.org) wrote:
>> On Tue, 18 Sep 2007 09:53:03 -0700 Vara Prasad <prasadav@...ibm.com> wrote:
>>
>>> This is part of the effort by the SystemTap team to move pieces of the 
>>> project that are generic to mainline.
>> Yeah.  It seems to have been reviewed to death.  Is it ready to
>> be applied yet?
> 
> I would just say that this could be seen rather as a driver tracing
> interface than a general purpose tracing interface. Therefore, maybe the
> name is a bit misleading ? And yes, what is there is good, but it does
> not seem to be a replacement for a generic kernel tracer.
> 
> My suggestions to turn it into a more suitable interface for a generic
> tracer are summarized in this email:
> http://lkml.org/lkml/2007/9/15/136
> 
> Mathieu
> 
Hi Mathieu
   Sorry I did not comment earlier on your email describing a generic 
tracer.  I believe that "trace" and your generic tracer could complement 
each other nicely.  The trace primitives could be expanded in the future 
to provide many of the features you described.  However, some of the 
features you describe are dependent on the format of the trace data 
itself (for example filtering), thus belong in a layer on top of trace.

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