All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [x86, paravirt] fd6f48529f: aim7.jobs-per-min -26.1% regression
Date: Fri, 09 Dec 2016 06:36:32 +0100	[thread overview]
Message-ID: <20161209053632.GE3061@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <87d1h13k1v.fsf@yhuang-dev.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

On Fri, Dec 09, 2016 at 10:36:44AM +0800, Huang, Ying wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
> 
> > On Thu, Dec 08, 2016 at 04:39:10PM +0800, Huang, Ying wrote:
> >
> >> >> in testcase: aim7
> >> >> on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 4 -m 5G
> >
> > One more question, what does the host system look like? Does that have 4
> > CPUs as well?
> 
> Yes.  The host system have 4 CPUs.

Thanks!

Ok, I eventually managed to reproduce and posted patches here:

  https://lkml.kernel.org/r/20161208154213.952687487(a)infradead.org

There were a bunch of factors that made it very hard for me to reproduce
this particular bug; the first being that I suck at virt stuff and I
couldn't get KVM to work on my usually dev box _at_all_.

I eventually managed to get KVM running on a HSW-EX :-)

Now, I also assumed (never assume) that it was the overloaded vcpu
scenario that was affected, because, well that's what the patches
attempt to 'fix'.

Playing with various setups of overload didn't in fact show regressions.

I also tried non-overloaded scenarios, but those didn't show the
regression! Until I ensured that all vCPUs were confined to a single
node -- so much for running things on a 4 node, 144 cpu system :-)


In any case, thanks for all the effort!

      reply	other threads:[~2016-12-09  5:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 18:07 [x86, paravirt] fd6f48529f: aim7.jobs-per-min -26.1% regression kernel test robot
2016-12-01  7:04 ` Peter Zijlstra
2016-11-30 23:17   ` Ye Xiaolong
2016-12-01  7:21     ` Peter Zijlstra
2016-12-01 16:49     ` Ye Xiaolong
2016-12-07 13:17 ` Peter Zijlstra
2016-12-08  1:12   ` Huang, Ying
2016-12-08  8:39   ` Huang, Ying
2016-12-08 11:08     ` Peter Zijlstra
2016-12-09  2:36       ` Huang, Ying
2016-12-09  5:36         ` Peter Zijlstra [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=20161209053632.GE3061@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=lkp@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.