Lines Matching +full:traces +full:- +full:db

1 The files in this directory help with testing Virgl on the virtio-gpu winsys 
22 $ sh perf-testing/build-dockerimage.sh
29 $ bash perf-testing/run_trace-in-container.sh \
30     --root $PATH_THAT_CONTAINS_MESA_CHECKOUT_VIRGLRENDERER_AND_TRACES_DB_CHECKOUT \
31     --trace $API_TRACE_TO_RUN
34 There are also options for run_trace-in-container.sh that allow specifying the 
35 path to mesa, virglrenderer, and the traces db. These override the root path. 
39 root that contains the traces db as subdirectory the the trace file name can be 
40 also given with this traces db sudirectory name, i.e. if the traces db is located 
41 in '$workdir/traces-db', root=$workdir,  and the trace is calles 'sometrace.trace', 
44   perf-testing/run_trace-in-container.sh -r $rootdir -t traces-db/sometrace.trace
48   perf-testing/run_trace-in-container.sh -r $rootdir -t sometrace.trace
52 At the moment of writing, the branch perfetto-tracing is needed for mesa at
55 emit the required traces.
57 The perfetto traces will be saved to the a subdirectory of the traces-db checkout 
58 directory with a name based on the api trace passed in with the --trace parameter. 
60 Once the run_trace-in-container.sh script finishes, 3 Perfetto trace files will be written: 
61 $(API_TRACE_TO_RUN%.*}-host.perfetto, $(API_TRACE_TO_RUN%.*}-guest.perfetto 
62 and $(API_TRACE_TO_RUN%.*}-summary.perfetto. The last one is the fusion of the two first.
64 In order to visualize the traces, the Perfetto UI needs to be running in a local 
68 $ perf-testing/perfetto-ui.sh