From: Huang, Ying <ying.huang@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [smpboot] 0aefb957de: -97.6% pigz.throughput and many others changes
Date: Thu, 10 Dec 2015 16:30:30 +0800 [thread overview]
Message-ID: <87d1ued7tl.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <566926EF.1000206@bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Daniel Wagner <daniel.wagner@bmw-carit.de> writes:
> On 12/10/2015 03:41 AM, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> git://internal_merge_and_test_tree
>> revert-0aefb957de5f2a1d9467126114146b6c793cf180-0aefb957de5f2a1d9467126114146b6c793cf180
>> commit 0aefb957de5f2a1d9467126114146b6c793cf180 ("smpboot: Add CPU
>> hotplug state variables instead of reusing CPU states")
>>
>>
>> =========================================================================================
>> compiler/cpufreq_governor/kconfig/rootfs/tbox_group/test/testcase:
>> gcc-4.9/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/lkp-ivb-d02/pwrite3/will-it-scale
>
> The only explanation I have for these regressions over all kind of test
> (cpu, disk, ...) is that one or more CPU did not boot at all. The
> changes done are not in the hot path unless a lot of CPU hotplug
> operations are going on. Which I presume is not the case.
>
> @lkp team: Is possible to get one of the dmesg if the regression is
> observed?
The dmesg is attached. And yes, only one CPU boot with the commit:
[ 1.121157] x86: Booted up 4 nodes, 1 CPUs
Best Regards,
Huang, Ying
[-- Attachment #2: kmsg.xz --]
[-- Type: application/x-xz, Size: 29096 bytes --]
next parent reply other threads:[~2015-12-10 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566926EF.1000206@bmw-carit.de>
2015-12-10 8:30 ` Huang, Ying [this message]
2015-12-10 2:41 [smpboot] 0aefb957de: -97.6% pigz.throughput and many others changes kernel test robot
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=87d1ued7tl.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--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.