linux-kernel - Re: [PATCH resend] tracing/events: convert NAPI's tracepoint via TRACE

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: <alpine.DEB.2.00.0908311407060.13931@gandalf.stny.rr.com>
Date:	Mon, 31 Aug 2009 14:09:04 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Xiao Guangrong <xiaoguangrong@...fujitsu.com>,
	David Miller <davem@...emloft.net>,
	Neil Horman <nhorman@...driver.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Wei Yongjun <yjwei@...fujitsu.com>,
	Netdev <netdev@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH resend] tracing/events: convert NAPI's tracepoint via
 TRACE_EVENT


On Mon, 31 Aug 2009, Ingo Molnar wrote:

> 
> * Xiao Guangrong <xiaoguangrong@...fujitsu.com> wrote:
> 
> > - Convert NAPI's tracepoint via TRACE_EVENT macro, the output information
> >   like below:
> 
> I think as long as it does not touch tracing infrastructure (which 
> your patches dont do in their current form) this should be 
> done/merged via the networking tree.

I agree, all changes that are in include/trace/events/ and trace point 
usage can stay within the subsystem tree.

> 
> [ There might be some small collisions in define_trace.h (because
>   these tracepoints move from legacy to new-style TRACE_EVENT() 
>   form) but that's OK. ]

But changes to anything in include/trace or kernel/trace needs to go 
throught the tracing subsystem. This includes a changes to define_trace.h.

Thanks,

-- Steve

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