Re: [patch 00/17] Tracepoints v4 for linux-next

[Masami Hiramatsu <mhiramat@redhat.com>]

Hi Mathieu,

As far as I can see, your patchset can be separated into
several series of patches. Would you think this series of
patches should be pushed at once, or could be pushed
individually?

I think it is hard to push all of them into kernel at once,
because it needs ACKs from several developers who maintain
traced subsystems.

So, I'd like to suggest you to separate series of patches,
and to push framework and instrumentation patches step by step.
What would you think about it?

Thank you,

Mathieu Desnoyers wrote:
> Hi,
> 
> Here is the newest release of the Tracepoints, following the feedback from Peter
> Zijlstra. The main change is the creation of include/trace/ as a placeholder
> from tracepoint headers.
> 
> The patchset applies over linux-next patch-v2.6.26-next-20080715 in this order :
> 
> #This a separate RCU update upon which the tracepoints depend
> rcu-read-sched.patch
> 
> tracepoints.patch
> tracepoints-documentation.patch
> tracepoints-samples.patch
> 
> lttng-instrumentation-irq.patch
> lttng-instrumentation-scheduler.patch
> lttng-instrumentation-timer.patch
> lttng-instrumentation-kernel.patch
> 
> lttng-instrumentation-filemap.patch
> lttng-instrumentation-swap.patch
> lttng-instrumentation-memory.patch
> lttng-instrumentation-page.patch
> lttng-instrumentation-hugetlb.patch
> 
> lttng-instrumentation-net.patch
> lttng-instrumentation-ipv4.patch
> lttng-instrumentation-ipv6.patch
> 
> ftrace-port-to-tracepoints.patch
> 
> Mathieu
> 

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com