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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
