lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 4 Sep 2014 09:33:43 +0100
From:	Peter Maydell <peter.maydell@...aro.org>
To:	"long.wanglong" <long.wanglong@...wei.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Russell King <linux@....linux.org.uk>, nico@...aro.org,
	Victor Kamensky <victor.kamensky@...aro.org>,
	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"ben.dooks@...ethink.co.uk" <ben.dooks@...ethink.co.uk>,
	santosh.shilimkar@...com,
	Christopher Covington <cov@...eaurora.org>,
	arm-mail-list <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [SMP BUG?] the return value of is_smp() is bug?

On 4 September 2014 02:13, long.wanglong <long.wanglong@...wei.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists