[PATCH 0/3] A kernel tracing interface - (updated)

[PATCH 0/3] A kernel tracing interface - (updated)

[David J. Wilder]

These patches provide a kernel tracing interface called "trace".

(update) Moved the sample code to the new samples\ subdir

The motivation for "trace" is to:
- Provide a simple set of tracing primitives that will utilize the high-
  performance and low-overhead of relayfs for passing traces data from
  kernel to user space.
- Provide a common user interface for managing kernel traces.
- Allow for binary as well as ascii trace data.
- Incorporate features from the systemtap runtime that are
  useful to others.

Patches are against 2.6.23-rc6-mm1

Summary of patches:
[patch 1/3]  Trace code and documentation
[patch 2/3]  Relay Reset Consumed
[patch 3/3]  Trace sample

Note: Patches 1/3 and 2/3 must be applied together.

Note: The following patches must be applied with 3/3.
[patch 3/5] Add samples subdir
	http://lkml.org/lkml/2007/9/25/157
[patch 4/5] Linux Kernel Markers - Samples
	http://lkml.org/lkml/2007/9/25/166

Signed-off-by: David Wilder <dwilder@us.ibm.com>

Re: [PATCH 0/3] A kernel tracing interface - (updated)

[Randy Dunlap]

On Wed, 26 Sep 2007 11:22:29 -0700 David J. Wilder wrote:

> These patches provide a kernel tracing interface called "trace".
> 
> (update) Moved the sample code to the new samples\ subdir
> 
> The motivation for "trace" is to:
> - Provide a simple set of tracing primitives that will utilize the high-
>   performance and low-overhead of relayfs for passing traces data from
>   kernel to user space.
> - Provide a common user interface for managing kernel traces.
> - Allow for binary as well as ascii trace data.
> - Incorporate features from the systemtap runtime that are
>   useful to others.
> 
> Patches are against 2.6.23-rc6-mm1
> 
> Summary of patches:
> [patch 1/3]  Trace code and documentation
> [patch 2/3]  Relay Reset Consumed
> [patch 3/3]  Trace sample
> 
> Note: Patches 1/3 and 2/3 must be applied together.

Patch 2 provides an interface that patch 1 needs, correct?
So yes, patches 1 & 2 need to be applied together (merged),
or their order could be reversed, yes?  Can't the Relay patch
be merged standalone without breaking anything?


> Note: The following patches must be applied with 3/3.
> [patch 3/5] Add samples subdir
> 	http://lkml.org/lkml/2007/9/25/157
> [patch 4/5] Linux Kernel Markers - Samples
> 	http://lkml.org/lkml/2007/9/25/166


---
~Randy
Phaedrus says that Quality is about caring.

Re: [PATCH 0/3] A kernel tracing interface - (updated)

[David Wilder]

Randy Dunlap wrote:
> On Wed, 26 Sep 2007 11:22:29 -0700 David J. Wilder wrote:
> 
>> These patches provide a kernel tracing interface called "trace".
>>
>> (update) Moved the sample code to the new samples\ subdir
>>
>> The motivation for "trace" is to:
>> - Provide a simple set of tracing primitives that will utilize the high-
>>   performance and low-overhead of relayfs for passing traces data from
>>   kernel to user space.
>> - Provide a common user interface for managing kernel traces.
>> - Allow for binary as well as ascii trace data.
>> - Incorporate features from the systemtap runtime that are
>>   useful to others.
>>
>> Patches are against 2.6.23-rc6-mm1
>>
>> Summary of patches:
>> [patch 1/3]  Trace code and documentation
>> [patch 2/3]  Relay Reset Consumed
>> [patch 3/3]  Trace sample
>>
>> Note: Patches 1/3 and 2/3 must be applied together.
> 
> Patch 2 provides an interface that patch 1 needs, correct?
Yes.
> So yes, patches 1 & 2 need to be applied together (merged),
> or their order could be reversed, yes?  
2/3 should be applied at the same time as 1/3,  or 2/3 can be applied 
standalone.  The order they are applied makes no difference.  But trace 
will not build if the relay patch is not applied.

Can't the Relay patch
> be merged standalone without breaking anything?

Yes the relay patch can be applied standalone.



> 
> 
>> Note: The following patches must be applied with 3/3.
>> [patch 3/5] Add samples subdir
>> 	http://lkml.org/lkml/2007/9/25/157
>> [patch 4/5] Linux Kernel Markers - Samples
>> 	http://lkml.org/lkml/2007/9/25/166
> 
> 
> ---
> ~Randy
> Phaedrus says that Quality is about caring.
> 

Re: [PATCH 0/3] A kernel tracing interface - (updated)

[Mathieu Desnoyers]

* David J. Wilder (dwilder@us.ibm.com) wrote:
> These patches provide a kernel tracing interface called "trace".
> 
> (update) Moved the sample code to the new samples\ subdir
> 
> The motivation for "trace" is to:
> - Provide a simple set of tracing primitives that will utilize the high-
>   performance and low-overhead of relayfs for passing traces data from
>   kernel to user space.
> - Provide a common user interface for managing kernel traces.
> - Allow for binary as well as ascii trace data.
> - Incorporate features from the systemtap runtime that are
>   useful to others.
> 
> Patches are against 2.6.23-rc6-mm1
> 
> Summary of patches:
> [patch 1/3]  Trace code and documentation
> [patch 2/3]  Relay Reset Consumed
> [patch 3/3]  Trace sample
> 
> Note: Patches 1/3 and 2/3 must be applied together.
> 
> Note: The following patches must be applied with 3/3.
> [patch 3/5] Add samples subdir
> 	http://lkml.org/lkml/2007/9/25/157

I guess you mean:
[patch 3/5] Add samples subdir (updated)
http://lkml.org/lkml/2007/9/25/366

(please try it with this new version, it should work as is..)

Mathieu

> [patch 4/5] Linux Kernel Markers - Samples
> 	http://lkml.org/lkml/2007/9/25/166
> 
> Signed-off-by: David Wilder <dwilder@us.ibm.com>
> 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

Re: [PATCH 0/3] A kernel tracing interface - (updated)

[David Wilder]

Mathieu Desnoyers wrote:
> * David J. Wilder (dwilder@us.ibm.com) wrote:
>> These patches provide a kernel tracing interface called "trace".
>>
>> (update) Moved the sample code to the new samples\ subdir
>>
>> The motivation for "trace" is to:
>> - Provide a simple set of tracing primitives that will utilize the high-
>>   performance and low-overhead of relayfs for passing traces data from
>>   kernel to user space.
>> - Provide a common user interface for managing kernel traces.
>> - Allow for binary as well as ascii trace data.
>> - Incorporate features from the systemtap runtime that are
>>   useful to others.
>>
>> Patches are against 2.6.23-rc6-mm1
>>
>> Summary of patches:
>> [patch 1/3]  Trace code and documentation
>> [patch 2/3]  Relay Reset Consumed
>> [patch 3/3]  Trace sample
>>
>> Note: Patches 1/3 and 2/3 must be applied together.
>>
>> Note: The following patches must be applied with 3/3.
>> [patch 3/5] Add samples subdir
>> 	http://lkml.org/lkml/2007/9/25/157
> 
> I guess you mean:
> [patch 3/5] Add samples subdir (updated)
> http://lkml.org/lkml/2007/9/25/366
> 
> (please try it with this new version, it should work as is..)

yes it works fine with the new version of your patch,  I will update my 
note for the next round of submissions.
> 
> Mathieu
> 
>> [patch 4/5] Linux Kernel Markers - Samples
>> 	http://lkml.org/lkml/2007/9/25/166
>>
>> Signed-off-by: David Wilder <dwilder@us.ibm.com>
>>
>>
>