On Jan 2, 2018, at 6:58 PM, kernel test robot
<xiaolong.ye(a)intel.com> wrote:
Greeting,
We noticed a -12.1% regression of hackbench.throughput due to commit:
commit: 11a1251e3a3cc9532f358c889deea63169bd2c65 ("x86/entry/64: Make
cpu_entry_area.tss read-only")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: hackbench
on test machine: 256 threads Phi with 96G memory
with following parameters:
nr_threads: 100%
mode: threads
ipc: pipe
cpufreq_governor: performance
test-description: Hackbench is both a benchmark and a stress test for the Linux kernel
scheduler.
test-url:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/sc...
Details are as below:
-------------------------------------------------------------------------------------------------->
To reproduce:
git clone
https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
=========================================================================================
compiler/kconfig/rootfs/sleep/tbox_group/testcase:
gcc-7/x86_64-kexec/debian-x86_64-2016-08-31.cgz/1/vm-lkp-wsx03-2G/boot
commit:
dff71e3c0e ("x86/entry: Clean up the SYSENTER_stack code")
11a1251e3a ("x86/entry/64: Make cpu_entry_area.tss read-only")
That's bizarre. How confident are your that this is attributed to the
right patch?
--Andy