From: Chen Baozi <baozich@gmail.com>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: Julien Grall <julien.grall@linaro.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen/arm: Support kick cpus and switch to hypervisor for the OMAP5
Date: Thu, 15 Aug 2013 19:28:48 +0800 [thread overview]
Message-ID: <CCEE098C-687B-4FA3-A34D-4FD158D2FC6A@gmail.com> (raw)
In-Reply-To: <CAGQvs6j8pJ-a6AKZDZjYqgMULeTfVqqC1Bfm-mE6ffv=4hQH-g@mail.gmail.com>
On Aug 15, 2013, at 7:23 PM, Andrii Anisov <andrii.anisov@globallogic.com> wrote:
> Following documentation I have, following code is odd:
>
> + ldr r2, =OMAP5_GIC_BASE_ADDRESS /* r2 := OMAP5 gic base address */
> + b kick_cpus_sgi
> kick_cpus_sgi:
>
> CPU1 on being waking by sev checks AUX_CORE_BOOT_0 if it's ok, branches to AUX_CORE_BOOT_1.
> And CPU1 comes to us in supervisor mode.
No, it doesn't. At least, on my board the early_printk log shows:
- CPU 00000001 booting -
- Machine ID 00000ec1 -
- Started in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
Cheers,
Baozi
next prev parent reply other threads:[~2013-08-15 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:16 [PATCH] xen/arm: Support kick cpus and switch to hypervisor for the OMAP5 Chen Baozi
2013-08-15 9:33 ` Tim Deegan
2013-08-15 9:34 ` Andrii Anisov
2013-08-15 9:48 ` Chen Baozi
2013-08-15 11:10 ` Andrii Anisov
2013-08-15 11:23 ` Chen Baozi
2013-08-15 11:27 ` Andrii Anisov
2013-08-15 11:23 ` Andrii Anisov
2013-08-15 11:28 ` Chen Baozi [this message]
[not found] ` <CAGQvs6jN8a7j8J5=+PNA_8Cc2jx22Gom86EXc9KdD=xf3NFiLA@mail.gmail.com>
[not found] ` <AFEC4CA5-C8E7-4D08-97DC-1C4C95AD03F9@gmail.com>
2013-08-15 12:01 ` Andrii Anisov
2013-08-15 10:03 ` Julien Grall
2013-08-15 11:19 ` Chen Baozi
2013-08-15 11:40 ` Julien Grall
2013-08-15 11:48 ` Chen Baozi
2013-08-15 12:10 ` 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=CCEE098C-687B-4FA3-A34D-4FD158D2FC6A@gmail.com \
--to=baozich@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=julien.grall@linaro.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).