1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
# Existing plugins
EZTrace ships several plugins for the main parallel programming libraries.
### MPI
The MPI plugin traces MPI communications (including non-blocking
collectives), and supports MPI communicators. It supports the C and
Fortran interfaces.
It does not support (yet) MPI-IO primitives.
### OpenMP
EZTrace ships two plugins for OpenMP:
- `ompt` uses the OMPT interface to trace OpenMP parallel regions, loops, task, etc.
- `openmp` intercepts calls to the GNU OpenMP runtime system. It can
only trace parallel region with GNU OpenMP. You can also instrument
your OpenMP application with Opari to collect more events (including
loops, tasks, ...), and to make it work with any OpenMP implementation
### Pthread
EZTrace traces pthread creation/destruction. You can also use the
`pthread` plugin to trace pthread synchronization functions
(eg. `pthread_mutex_*`, `pthread_cond_*`.
### PosixIO
EZTrace `posixio` plugin traces calls to PosixIO functions (`open`,
`read`, `write`, `dup`, `fread`, `fwrite`, ...
### Memory
EZTrace `memory` plugin traces calls to dynamic memory allocation functions (`malloc`,
`realloc`, `calloc`, `free`, ...
### IOTracer
EZTrace `iotracer` plugin uses IOTracer to trace IO events that happen
within the Linux kernel. See [EZIOTracer webpage](https://gitlab.com/idiom1/eziotrace)
for instructions.
### CUDA
EZTrace `cuda` plugin traces CUDA events (memory copy, kernel
invocation, etc.) This plugin is currently not supported (we need to
port it to use the OTF2 trace format)
### StarPU
EZTrace `starpu` plugin traces [StarPU](https://starpu.gitlabpages.inria.fr/)
events (task creation, task execution, etc.)
This plugin is currently not supported (we need to
port it to use the OTF2 trace format)
### PAPI
EZTrace `papi` plugin collect harware counters using the PAPI library.
This plugin is currently not supported (we need to
port it to use the OTF2 trace format)
# Generating custom plugins
** NOT IMPLEMENTED IN EZTRACE-2.0 yet ! **
You can generate one plugin and instrument the functions you want to.
In order to generate your plugin, you need to create a file containing:
* The name of the library you want to trace (libNAME.so)
* A brief description of the library (optional)
* An ID to identify the module (0? is reserved for eztrace internal use. Thus,
you can use any between 10 and ff)
* The prototype of the functions you want to instrument
Basically, the file should look like that:
BEGIN_MODULE
NAME example_lib
DESC "module for the example library"
ID 99
int example_do_event(int n)
double example_function1(double* array, int array_size)
END_MODULE
Now use eztrace_create_plugin to generate the plugin source code:
$ eztrace_create_plugin example.tpl
New Module
Module name: 'example_lib'
Module description: '"module for the example library"'
Module id: '99'
emulate record_state for 'example_do_event'
Function 'example_do_event' done
emulate record_state for 'example_function1'
Function 'example_function1' done
End of Module example_lib
The source code is generated in the output directory. Just type:
$ make
Now set the EZTRACE_LIBRARY_PATH to the appropriate directory and you are good
to go.
You can also specify (in the example.tpl file) the way a function is depicted in
the output trace. For instance:
int submit_job(int* array, int array_size)
BEGIN
ADD_VAR("job counter", 1)
END
Specifies that when the submit_job function is called, the output trace should
increment the "job counter" variable. You can now track the value of a variable!
The test/module_generator directory contains several scripts that demonstrate
the various commands available.
|
