From: Ingo Molnar <mingo@kernel.org>
To: kernel test robot <ying.huang@intel.com>
Cc: Andy Lutomirski <luto@kernel.org>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Denys Vlasenko <dvlasenk@redhat.com>
Subject: Re: [lkp] [x86/build] b2c51106c75: -18.1% will-it-scale.per_process_ops
Date: Wed, 5 Aug 2015 10:38:58 +0200 [thread overview]
Message-ID: <20150805083858.GA21506@gmail.com> (raw)
In-Reply-To: <87pp37y4cy.fsf@yhuang-dev.intel.com>
* kernel test robot <ying.huang@intel.com> wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm
> commit b2c51106c7581866c37ffc77c5d739f3d4b7cbc9 ("x86/build: Fix detection of GCC -mpreferred-stack-boundary support")
Does the performance regression go away reproducibly if you do:
git revert b2c51106c7581866c37ffc77c5d739f3d4b7cbc9
?
Thanks,
Ingo
next prev parent reply other threads:[~2015-08-05 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 5:17 [lkp] [x86/build] b2c51106c75: -18.1% will-it-scale.per_process_ops kernel test robot
2015-08-05 8:38 ` Ingo Molnar [this message]
2015-08-10 20:39 ` Andy Lutomirski
2015-09-02 2:40 ` Huang Ying
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=20150805083858.GA21506@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).