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: <450AEC92.7090409@us.ibm.com>
Date:	Fri, 15 Sep 2006 13:10:26 -0500
From:	"Jose R. Santos" <jrs@...ibm.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Roman Zippel <zippel@...ux-m68k.org>,
	Tim Bird <tim.bird@...sony.com>, Ingo Molnar <mingo@...e.hu>,
	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

Alan Cox wrote:
> Consistency for user space ?
>   

With several other trace tools being implemented for the kernel, there 
is a great problem with consistencies among these tool.  It is my 
opinion that trace are of very little use to _most_ people with out the 
availability of post-processing tools to analyses these trace.  While I 
wont say that we need one all powerful solution, it would be good if all 
solutions would at least be able to talk to the same post-processing 
facilities in user-space.  Before LTTng is even considered into the 
kernel, there need to be discussion to determine if the trace mechanism 
being propose is suitable for all people interested in doing trace 
analysis.  The fact the there also exist tool like LKET and LKST seem to 
suggest that there other things to be considered when it comes to 
implementing a trace mechanism that everyone would be happy with.

It would also be useful for all the trace tool to implement the same 
probe points so that post-processing tools can be interchanged between 
the various trace implementations.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ