From: Andre Przywara <andre.przywara@linaro.org>
To: Julien Grall <julien.grall@citrix.com>
Cc: Tim Deegan <tim@xen.org>, Chen Baozi <baozich@gmail.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: xen: arm: beginning the removal of mode_switch.S
Date: Wed, 21 Aug 2013 14:42:22 +0200 [thread overview]
Message-ID: <5214B5AE.5040401@linaro.org> (raw)
In-Reply-To: <5214B43C.7090807@citrix.com>
On 08/21/2013 02:36 PM, Julien Grall wrote:
> On 08/20/2013 03:11 PM, Ian Campbell wrote:
>> So this is all pretty complex (not to mention hard to describe in ASCII)
>> and in lockstep, the secondary cpus wait twice once on the original
>> smp_cpu_up and then again on the relocated version. There is a subtle
>> reliance on the 1:1 mapping being retained in the original copy of the
>> page tables.
>
> Thanks for this ASCII!
>
>> I think the original wait is actually a workaround for lack of firmware
>> on the fastmodels, and should be implemented by either the firmware or
>> bootwrapper.
>
> BTW, this wait is an issue when the boot CPU ID is not equal to 0.
>
> I gave a quick try to move kick cpus after the HYP mode switch in
> assembly and I'm unable to boot secondary cpus on the Versatile Express.
> I guess, on the VE secondary cpus can only be "kick" in secure mode.
Right, but I think this is not specific to the VE, but ARM in general.
If I remember correctly the reason was that you cannot send IPIs from an
non-secure GIC CPU interface to a secure one. So you have to enable the
CPU interfaces of the others cores for non-secure operation first, which
involves waking them up.
In my U-Boot code I switch to HYP mode on the BSP at the very end, after
having switched the secondary cores to HYP before.
Regards,
Andre.
next prev parent reply other threads:[~2013-08-21 12:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 11:51 xen: arm: beginning the removal of mode_switch.S Ian Campbell
2013-08-15 13:46 ` Tim Deegan
2013-08-15 14:07 ` Ian Campbell
2013-08-15 16:53 ` Tim Deegan
2013-08-15 20:48 ` Ian Campbell
2013-08-15 17:05 ` Julien Grall
2013-08-15 20:51 ` Ian Campbell
2013-08-16 10:12 ` Julien Grall
2013-08-16 15:04 ` Ian Campbell
2013-08-16 15:11 ` Andre Przywara
2013-08-16 15:44 ` Julien Grall
2013-08-20 14:11 ` Ian Campbell
2013-08-21 12:36 ` Julien Grall
2013-08-21 12:42 ` Andre Przywara [this message]
2013-08-22 7:19 ` Ian Campbell
2013-08-15 20:55 ` Andre Przywara
2013-08-15 21:14 ` Ian Campbell
2013-08-19 17:46 ` Christoffer Dall
2013-08-20 9:37 ` Ian Campbell
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=5214B5AE.5040401@linaro.org \
--to=andre.przywara@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=baozich@gmail.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).