From 9f12816451e51958806f61298d180a4a570efa11 Mon Sep 17 00:00:00 2001 From: "Yan, Like" Date: Thu, 29 Mar 2018 14:11:04 +0800 Subject: [PATCH] DM:tools: add README.rst for acrntrace Reviewed-by: Zhao Yakui Signed-off-by: Yan, Like Acked-by: Eddie Dong --- tools/acrntrace/README.rst | 49 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 tools/acrntrace/README.rst diff --git a/tools/acrntrace/README.rst b/tools/acrntrace/README.rst new file mode 100644 index 000000000..7e6497fa9 --- /dev/null +++ b/tools/acrntrace/README.rst @@ -0,0 +1,49 @@ +acrntrace +######### + +DESCRIPTION +########### +acrntrace: is a tool running on SOS, to capture trace data. +scripts directory includes scripts to analyze the trace data. + +USAGE +##### +Capture trace data on SOS + + 1) Launch acrntrace + Capture buffered trace data: + # acrntrace + or clear buffer before tracing start: + # acrntrace -c + Trace files are created under /tmp/acrntrace/, directory name with time + string eg: 20171115-101605 + 2) To stop acrntrace + # q + 3) Copy the trace data to linux pc + # scp -r /tmp/acrntrace/20171115-101605/ xxx@10.239.142.239:/home/xxxx/t + race_data + +Analyze the trace data on Linux PC + + 1) Run the python script to analyze the vm_exits: + # acrnalyze.py -i /home/xxxx/trace_data/20171115-101605/0 -o /home/xxxx/trac + e_data/20171115-101605/cpu0 --vm_exit + - "--vm_exit" specify the analysis to do, currently, only vm_exit analysis + is supported. + - A preprocess would be taken out to make the trace data start and end with + an VM_ENTER, and a copy of original data file is saved with suffix ".orig"; + - Analysis report would be given on the std output and in a csv file with + name specified via "-o outpu_file"; + Script usage: + [Usage] acrnalyze.py [options] [value] ... + [options] + -h: print this message + -i, --ifile=[string]: input file + -o, --ofile=[string]: output file + --vm_exit: to generate vm_exit report + + The scripts require bash and python2. + +BUILD +##### +# make