From: Leon Yu <"Leon Yu"@ccca.nctu.edu.tw>
To: linux-kernel@vger.kernel.org
Subject: Re: [SMP BUG?] the return value of is_smp() is bug?
Date: Tue, 2 Sep 2014 04:40:44 +0000 (UTC) [thread overview]
Message-ID: <lu3hoc$lrl$1@ger.gmane.org> (raw)
In-Reply-To: 1409570133-2766-1-git-send-email-long.wanglong@huawei.com
On 2014-09-01, Wang Long <long.wanglong@huawei.com> wrote:
>
> Hi,all
>
> In kernel 3.17-rc2, when i set CONFIG_HAVE_SMP = y and CONFIG_SMP_ON_UP = y
> in .config file. the secondary core can not boot.
>
> when i set CONFIG_HAVE_SMP = y and CONFIG_SMP_ON_UP = n in .config file,
> the secondary core can boot.
>
> But this does not happen in kernel 3.10 lts kernel, Whether the
> CONFIG_SMP_ON_UP is set yes or no ,the secondary core can boot.
>
> Does the meaning of CONFIG_SMP_ON_UP changed or this is a bug in kernel3.17-rc2 ?
Update qemu to at least 2.0.
qemu of older version fails to smp-boot Linux 3.12+ with CONFIG_SMP_ON_UP
enabled.
-Leon
next prev parent reply other threads:[~2014-09-02 4:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 11:15 [SMP BUG?] the return value of is_smp() is bug? Wang Long
2014-09-01 11:15 ` Wang Long
2014-09-02 4:40 ` Leon Yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-01 11:35 Wang Long
2014-09-01 11:35 ` Wang Long
2014-09-01 8:49 ` Arnd Bergmann
2014-09-01 8:49 ` Arnd Bergmann
2014-09-01 10:19 ` Russell King - ARM Linux
2014-09-01 10:19 ` Russell King - ARM Linux
2014-09-04 1:01 ` long.wanglong
2014-09-04 1:01 ` long.wanglong
2014-09-01 5:49 Wang Long
2014-09-01 5:49 ` Wang Long
2014-09-01 10:00 ` long.wanglong
2014-09-01 10:00 ` long.wanglong
2014-09-01 10:26 ` Arnd Bergmann
2014-09-01 10:26 ` Arnd Bergmann
2014-09-04 1:13 ` long.wanglong
2014-09-04 1:13 ` long.wanglong
2014-09-04 8:33 ` Peter Maydell
2014-09-04 8:33 ` Peter Maydell
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='lu3hoc$lrl$1@ger.gmane.org' \
--to="leon yu"@ccca.nctu.edu.tw \
--cc=chianglungyu@gmail.com \
--cc=linux-kernel@vger.kernel.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.