From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: [x86-tip] strange nr_cpus= boot regression
Date: Tue, 27 Sep 2016 05:13:37 +0200 [thread overview]
Message-ID: <1474946017.3801.19.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609261525340.5483@nanos>
On Mon, 2016-09-26 at 15:35 -0400, Thomas Gleixner wrote:
> On Mon, 26 Sep 2016, Thomas Gleixner wrote:
> > Can you please provide your .config and the dmesg of a bad and a good run?
>
> Don't bother. I found it.
>
> It's a merge artifact. So git bisect pointing at the merge commit is
> entirely correct.
>
> mainline moves
>
> > num_processors++;
>
> to a different place in the function. See commit c291b0151585.
>
> Now the nodeid patch set in x86/apic does not have this commit and so
> f7c28833c2520 removes num_processors++ from the original location before
> c291b0151585.
Whew, no mythical creature infestation. Thanks, next encounter with
such an artifact should provide markedly less entertainment.
-Mike
next prev parent reply other threads:[~2016-09-27 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 12:29 [x86-tip] strange nr_cpus= boot regression Mike Galbraith
2016-09-26 12:39 ` Mike Galbraith
2016-09-26 13:40 ` Borislav Petkov
2016-09-26 14:15 ` Borislav Petkov
2016-09-26 14:27 ` Mike Galbraith
2016-09-26 17:36 ` Thomas Gleixner
2016-09-26 17:52 ` Thomas Gleixner
2016-09-26 19:35 ` Thomas Gleixner
2016-09-26 19:56 ` Thomas Gleixner
2016-09-27 3:13 ` Mike Galbraith [this message]
2016-09-27 4:09 ` Borislav Petkov
2016-09-27 2:07 ` Dou Liyang
2016-09-27 12:16 ` Thomas Gleixner
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=1474946017.3801.19.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bp@alien8.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.