пон, 22. јун 2020. у 12:31 Ahmed Karaman <ahmedkhaledkara...@gmail.com> је написао/ла: > > Greetings, > > Welcome to the TCG Continuous Benchmarking GSoC project! > This is the first report in a series that will be posted here on the > mailing list as part of the project. > > During the project, multiple Linux profiling tools will be used. > These tools will help you profile your different QEMU execution > scenarios, and locate performance bottlenecks as well as performance > regression problems. > > To provide you with a better understanding of these tools, this report > presents two of them - Perf and Callgrind. > It starts with measuring the basic performance metrics when running > a program using both tools, then it proceeds to calculating the top 25 > most executed functions in QEMU. > To dissect the output of each of the two tools, a separate section > for comparing the output results is presented which focuses on how > these results apply to QEMU. > Finally, a stability test is devised that compares how the output > of the two tools differ with each subsequent invocation of QEMU. > > For easier accessibility, all reports will be hosted on a dedicated > website: > https://ahmedkrmn.github.io/TCG-Continuous-Benchmarking/ > > Link to the first report: > https://ahmedkrmn.github.io/TCG-Continuous-Benchmarking/Measuring-Basic-Performance-Metrics-of-QEMU/ >
In introductory section on Callgrind, maybe you could add the general form of command line that performs profiling using Callgrind, something like this: valgrind --tool=callgrind [callgrind options] prog [prog options] Not a big deal, you can do some fine adjustments throughout the project. Thanks, Aleksandar > Best regards, > Ahmed Karaman
