From: Borislav Petkov <bp@alien8.de>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
tipbuild@zytor.com, lkp@01.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [lkp] [x86/copy_user] adb402cd14: will-it-scale.per_process_ops -12.7% regression
Date: Wed, 9 Nov 2016 13:42:14 +0100 [thread overview]
Message-ID: <20161109124214.sjasqcurv6gi64ol@pd.tnic> (raw)
In-Reply-To: <20161107025038.GE21529@yexl-desktop>
On Mon, Nov 07, 2016 at 10:50:38AM +0800, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -12.7% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit adb402cd1461eef6e1a21db4532a3b9e6a6be853 ("x86/copy_user: Unify the code by removing the 64-bit asm _copy_*_user() variants")
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm
>
> in testcase: will-it-scale
> on test machine: 8 threads Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz with 4G memory
> with following parameters:
>
> test: poll1
> cpufreq_governor: performance
...
> # Lock Debugging (spinlocks, mutexes, etc...)
> #
> # CONFIG_DEBUG_RT_MUTEXES is not set
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_DEBUG_MUTEXES is not set
> # CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
> # CONFIG_DEBUG_LOCK_ALLOC is not set
> # CONFIG_PROVE_LOCKING is not set
> # CONFIG_LOCK_STAT is not set
> CONFIG_DEBUG_ATOMIC_SLEEP=y
^^^^^^^^^^^^^^^^^^^^^^^^^
So Mel says that this might be the culprit for the observed
change in perf. Can you please rerun your test without that
CONFIG_DEBUG_ATOMIC_SLEEP thing?
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2016-11-09 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:50 [lkp] [x86/copy_user] adb402cd14: will-it-scale.per_process_ops -12.7% regression kernel test robot
2016-11-07 9:56 ` Borislav Petkov
2016-11-09 12:42 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161109124214.sjasqcurv6gi64ol@pd.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
--cc=torvalds@linux-foundation.org \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox