From: Borislav Petkov <bp@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
"Denys Vlasenko" <dvlasenk@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Brian Gerst" <brgerst@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
lkp@01.org, "Thomas Gleixner" <tglx@linutronix.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement
Date: Thu, 25 Aug 2016 13:45:06 +0200 [thread overview]
Message-ID: <20160825114506.GA11762@nazgul.tnic> (raw)
In-Reply-To: <D6903D5A-D2CA-4FAB-8D3E-5885B8F79AED@zytor.com>
On Thu, Aug 25, 2016 at 03:05:19AM -0700, H. Peter Anvin wrote:
> I'm wondering if one of those 23 invocations sets up some kind of
> corrupt data that continues to get used.
That could be one plausible explanation. Look at what calls
__sw_hweight64:
initmem_init
numa_policy_init
page_writeback_init
paging_init
pcpu_embed_first_chunk
pcpu_setup_first_chunk
sched_init
set_rq_online.part.46
setup_arch
setup_per_cpu_areas
update_sysctl
x86_64_start_kernel
x86_64_start_reservations
x86_numa_init
zone_sizes_init
I could very well imagine per CPU areas or some sched structure or
whatever getting silently corrupted.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-08-25 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 14:26 kernel test robot
2016-08-16 16:59 ` H. Peter Anvin
2016-08-16 17:16 ` Borislav Petkov
2016-08-16 23:09 ` H. Peter Anvin
2016-08-17 5:46 ` Borislav Petkov
2016-08-17 22:29 ` [LKP] " Huang, Ying
2016-08-18 3:45 ` Borislav Petkov
2016-08-18 3:54 ` Huang, Ying
2016-08-18 4:11 ` Borislav Petkov
2016-08-25 9:22 ` Borislav Petkov
2016-08-25 10:05 ` H. Peter Anvin
2016-08-25 11:45 ` Borislav Petkov [this message]
2016-08-25 20:07 ` H. Peter Anvin
2016-08-18 3:57 ` H. Peter Anvin
2016-08-17 6:48 ` Peter Zijlstra
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=20160825114506.GA11762@nazgul.tnic \
--to=bp@suse.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ville.syrjala@linux.intel.com \
--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
all inboxes | Powered by JetHome®