Greeting, FYI, we noticed a -2.4% regression of will-it-scale.per_process_ops due to commit: commit: d1de9d10dbdac46e9f45325252464eaf2a386388 ("EXPERIMENTAL: Diagnostics for lost timer events") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: will-it-scale on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 4 -m 5G with following parameters: test: lseek2 test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two. test-url: https://github.com/antonblanchard/will-it-scale Details are as below: --------------------------------------------------------------------------------------------------> To reproduce: git clone https://github.com/intel/lkp-tests.git cd lkp-tests bin/lkp qemu -k job-script # job-script is attached in this email testcase/path_params/tbox_group/run: will-it-scale/lseek2/vm-lkp-a03 eb14701b75404199 d1de9d10dbdac46e9f45325252 ---------------- -------------------------- 12930 ± 5% 741% 108810 will-it-scale.time.involuntary_context_switches 224 222 will-it-scale.time.system_time 124 122 will-it-scale.time.percent_of_cpu_this_job_got 2808016 2741901 will-it-scale.per_process_ops 62.29 60.73 will-it-scale.time.user_time 1839998 -4% 1769496 will-it-scale.per_thread_ops 1654 ± 7% 169% 4457 ± 3% vmstat.system.cs 3008 33% 4013 ± 4% vmstat.system.in 81.23 5% 85.58 boot-time.boot 217 5% 228 boot-time.idle 16.34 4% 16.93 boot-time.dhcp 16.43 4% 17.01 boot-time.kernel_boot 7057 ± 39% 2e+05 215369 ±165% latency_stats.avg.max Disclaimer: Results have been estimated based on internal Intel analysis and are provided for informational purposes only. Any difference in system hardware or software design or configuration may affect actual performance. Thanks, Xiaolong