Daniel P Berrange writes: > Describe use of per-subdir trace events files and how it impacts > code generation.
> Signed-off-by: Daniel P. Berrange <berra...@redhat.com> > --- > docs/tracing.txt | 61 > +++++++++++++++++++++++++++++++++++++++++++++++--------- > 1 file changed, 52 insertions(+), 9 deletions(-) > diff --git a/docs/tracing.txt b/docs/tracing.txt > index f351998a..3262a61 100644 > --- a/docs/tracing.txt > +++ b/docs/tracing.txt > @@ -27,18 +27,51 @@ for debugging, profiling, and observing execution. > == Trace events == > +=== Sub-directory setup === > + > Each directory in the source tree can declare a set of static trace events > -in a "trace-events" file. Each trace event declaration names the event, its > -arguments, and the format string which can be used for pretty-printing: > +in a "trace-events" file. The first (non-comment) statement in the file > +must be "@id_offset(NN)" where NN is an integer that is unique among all > +"trace-events" files in the QEMU source tree. The IDs can be arbitrarily > +chosen, but for extra fun the current "trace-events" files use values from > +the "powerful number" integer sequence :-) I think that the description of @id_offset is a leftover from a previous version of the series. Cheers, Lluis
