From: Peter Maydell <peter.maydell@linaro.org>
To: "long.wanglong" <long.wanglong@huawei.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@arm.linux.org.uk>,
nico@linaro.org, Victor Kamensky <victor.kamensky@linaro.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
"ben.dooks@codethink.co.uk" <ben.dooks@codethink.co.uk>,
santosh.shilimkar@ti.com,
Christopher Covington <cov@codeaurora.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: [SMP BUG?] the return value of is_smp() is bug?
Date: Thu, 4 Sep 2014 09:33:43 +0100 [thread overview]
Message-ID: <CAFEAcA82zX-yodXYB+4vVrjq7tVe=wV4v3iCQ7O1a1HLFX_B1w@mail.gmail.com> (raw)
In-Reply-To: <5407BCAE.7030606@huawei.com>
On 4 September 2014 02:13, long.wanglong <long.wanglong@huawei.com> wrote:
> When i revert the commit bc41b8724f24, the secondary core can boot.
> The problem is that qemu doesn't provide emulation of the SCU base
> address register. When reading the SCU base, qemu just return 0.
You need to upgrade your QEMU -- we improved the emulation
of all our Cortex-A9 boards to make sure they set valid values
for the base address register, in order to fix exactly this regression.
QEMU 2.0 or later should work.
(As an aside, I think the Aegis quirk test is pretty ugly:
"base address happens to be set to zero" is not exactly
a very reliable way to identify a particular SoC. However
in this case QEMU was emulating real h/w insufficiently
accurately, so we fixed it.)
thanks
-- PMM
next prev parent reply other threads:[~2014-09-04 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 5:49 [SMP BUG?] the return value of is_smp() is bug? Wang Long
2014-09-01 10:00 ` long.wanglong
2014-09-01 10:26 ` Arnd Bergmann
2014-09-04 1:13 ` long.wanglong
2014-09-04 8:33 ` Peter Maydell [this message]
2014-09-01 11:15 Wang Long
2014-09-02 4:40 ` Leon Yu
2014-09-01 11:35 Wang Long
2014-09-01 8:49 ` Arnd Bergmann
2014-09-01 10:19 ` Russell King - ARM Linux
2014-09-04 1:01 ` long.wanglong
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='CAFEAcA82zX-yodXYB+4vVrjq7tVe=wV4v3iCQ7O1a1HLFX_B1w@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=arnd@arndb.de \
--cc=ben.dooks@codethink.co.uk \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=long.wanglong@huawei.com \
--cc=nico@linaro.org \
--cc=santosh.shilimkar@ti.com \
--cc=victor.kamensky@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).