linux-kernel - Re: [RFC PATCH 00/28] ktap: A lightweight dynamic tracing tool for Linux

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]

Date:	Sat, 29 Mar 2014 09:46:01 +0800
From:	Jovi Zhangwei <jovi.zhangwei@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC PATCH 00/28] ktap: A lightweight dynamic tracing tool for Linux

On Sat, Mar 29, 2014 at 12:08 AM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Fri, Mar 28, 2014 at 09:47:21AM -0400, Jovi Zhangwei wrote:
>> Hi All,
>>
>> The following set of patches add ktap tracing tool.
>
> Yeah!
>
> Thanks for putting this patch set together, it looks good.
>
> But, why hide the kernel portions of ktap in the tools/ directory?  Is
> that ok with everyone else?  I don't expect to see kernel code burried
> in that directory, so any kernel API changes that might happen, might
> not get propagated into that location.
>
Reasonable, I will try to put kernel module side into kernel/trace/ktap
directory in next version.

There have some duplicated code with kernel/trace/*.c, then maybe
we can integrate it if ktap location more closer with ftrace.

Thanks for this suggestion.

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