tau_merge(1) [debian man page]

TAU_MERGE(1)							       Tools							      TAU_MERGE(1)

NAME

       tau_merge - combine multiple node and or thread TAU tracefiles into a merged tracefile

SYNOPSIS

       tau_merge [-a] [-r] [-n] [-e eventfile_list] [-m output_eventfile] {tracefile_list} [{output_tracefile} { - }]

DESCRIPTION

       tau_merge is generated when TAU is configured with the -TRACE option.

       This tool assembles a set of tau trace and event files from multiple multiple nodes or threads across a program's execution into a single
       unified trace file. Many TAU trace file tools operate on merged trace files.

       Minimally, tau_merge must be invoked with a list of unmerged trace files followed by the desired name of the merged trace file or the -
       flag to send the output to the standard out. Typically the list can be designated by giving the shared name of the trace files to be merged
       followed by desired range of thread or node designators in brackets or the wild card character '*' to encompass variable thread and node
       designations in the filename (trace.A.B.C.trc where A, B and C are the node, context and thread numbers respectively). For example
       tautrace.*.trc would represent all tracefiles in a given directory while tautrace.[0-5].0.0.trc would represent the tracefiles of nodes 0
       through 5 with context 0 and thread 0.

       tau_merge will generate the specified merged trace file and an event definition file, tau.edf by default.

       The event definition file can be given an alternative name by using the '-m' flag followed by the desired filename. A list of event
       definition files to be merged can be designated explicitly by using the '-e' flag followed by a list of unmerged .edf files, specified in
       the same manner as the trace file list.

       If computational resources are insufficient to merge all trace and event files simultaneously the process may be undertaken hierarchically.
       Corresponding subsets of the tracefiles and eventfiles may be merged in sequence to produce a smaller set of files that can then be to
       merged into a singular fully merged tracefile and eventfile. E.g. for a 100 node trace, trace sets 1-10, 11-20, ..., 91-100 could be merged
       into traces 1a, 2a, ..., 10a. Then 1a-10a could be merged to create a fully merged tracefile.

OPTIONS

       -e eventfile_list explicitly define the eventfiles to be merged

       -m output_eventfile explicitly name the merged eventfile to be created

       - send the merged tracefile to the standard out

       -a adjust earliest timestamp time to zero

       -r do not reassemble long events

       -n do not block waiting for new events. By default tau_merge will block and wait for new events to be appended if a tracefile is
       incomplete. This command allows offline merging of (potentially) incomplete tracefiles.

EXAMPLES

       To merge all TAU tracefiles into app.trc and produce a merged tau.edf eventfile:

       tau_merge *.trc app.trc

       To merge all eventfiles 0-255 into ev0_255merged.edf and TAU tracefiles for nodes 0-255 into the standard out:

       tau_merge -e events.[0-255].edf -m ev0_255merged.edf 
	 tautrace.[0-255].*.trc -

       To merge eventfiles 0, 5 and seven info ev057.edf and tau tracefiles for nodes 0, 5 and 7 with context and thread 0 into app.trc:

       tau_merge -e events.0.edf events.5.edf events.7.edf -m ev057.edf 
	 tautrace.0.0.0.trc tautrace.5.0.0.trc tautrace.7.0.0.trc app.trc

SEE ALSO

       tau_convert

       tau2profile

       tau2vtf

       tau2elg

       tau2slog2

								    12/22/2005							      TAU_MERGE(1)

TRACE-CMD-RESTORE(1)													      TRACE-CMD-RESTORE(1)

NAME

       trace-cmd-restore - restore a failed trace record

SYNOPSIS

       trace-cmd restore [OPTIONS] [command] cpu-file [cpu-file ...]

DESCRIPTION

       The trace-cmd(1) restore command will restore a crashed trace-cmd-record(1) file. If for some reason a trace-cmd record fails, it will
       leave a the per-cpu data files and not create the final trace.dat file. The trace-cmd restore will append the files to create a working
       trace.dat file that can be read with trace-cmd-report(1).

       When trace-cmd record runs, it spawns off a process per CPU and writes to a per cpu file usually called trace.dat.cpuX, where X represents
       the CPU number that it is tracing. If the -o option was used in the trace-cmd record, then the CPU data files will have that name instead
       of the trace.dat name. If a unexpected crash occurs before the tracing is finished, then the per CPU files will still exist but there will
       not be any trace.dat file to read from. trace-cmd restore will allow you to create a trace.dat file with the existing data files.

OPTIONS

       -c
	   Create a partial trace.dat file from the machine, to be used with a full trace-cmd restore at another time. This option is useful for
	   embedded devices. If a server contains the cpu files of a crashed trace-cmd record (or trace-cmd listen), trace-cmd restore can be
	   executed on the embedded device with the -c option to get all the stored information of that embedded device. Then the file created
	   could be copied to the server to run the trace-cmd restore there with the cpu files.

	       If *-o* is not specified, then the file created will be called
	       'trace-partial.dat'. This is because the file is not a full version
	       of something that trace-cmd-report(1) could use.

       -t tracing_dir
	   Used with -c, it overrides the location to read the events from. By default, tracing information is read from the debugfs/tracing
	   directory.  -t will use that location instead. This can be useful if the trace.dat file to create is from another machine. Just tar
	   -cvf events.tar debugfs/tracing and copy and untar that file locally, and use that directory instead.

       -k kallsyms
	   Used with -c, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used.  -k will override the file to read
	   the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file
	   locally, and use -k to point to that file.

       -o output'
	   By default, trace-cmd restore will create a trace.dat file (or trace-partial.dat if -c is specified). You can specify a different file
	   to write to with the -o option.

       -i input
	   By default, trace-cmd restore will read the information of the current system to create the initial data stored in the trace.dat file.
	   If the crash was on another machine, then that machine should have the trace-cmd restore run with the -c option to create the trace.dat
	   partial file. Then that file can be copied to the current machine where trace-cmd restore will use -i to load that file instead of
	   reading from the current system.

EXAMPLES

       If a crash happened on another box, you could run:

	   $ trace-cmd restore -c -o box-partial.dat

       Then on the server that has the cpu files:

	   $ trace-cmd restore -i box-partial.dat trace.dat.cpu0 trace.dat.cpu1

       This would create a trace.dat file for the embedded box.

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
       trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

NOTES

	1. rostedt@goodmis.org
	   mailto:rostedt@goodmis.org

								    06/11/2014						      TRACE-CMD-RESTORE(1)