From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [Question] Verification For arm64: suspend/resume implementation
Date: Tue, 24 Sep 2013 14:00:13 +0100 [thread overview]
Message-ID: <20130924130012.GE25907@arm.com> (raw)
In-Reply-To: <52417C4D.1030009@marvell.com>
On Tue, Sep 24, 2013 at 12:49:33PM +0100, Leo Yan wrote:
> On 09/24/2013 05:02 PM, Achin Gupta wrote:
> > On Tue, Sep 24, 2013 at 03:00:38AM +0100, Leo Yan wrote:
> >> Here have another question, ARM have the example code for boot wrapper
> >> which will switch from EL3 to secure EL1 rather than non-secure's EL1?
> >
> > I dont' think we do but let me check. Switching to S-EL1 instead of
> > NS-EL1 should be a matter of _not_ setting the SCR_EL3.NS bit before
> > doing the exception level change (ERET).
>
> I quick try with below patch for boot wrapper, i saw foundataion model
> cannot boot up successfully and there have no console output; suppose
> it's hang at some boot operations, but now foundation model cannot debug
> low level code, so i cannot debug further more. :-(
>
> diff --git a/boot.S b/boot.S
> index a1f25e2..2f1b867 100644
> --- a/boot.S
> +++ b/boot.S
> @@ -19,7 +19,6 @@ _start:
> b.ne start_ns // skip EL3 initialisation
>
> mov x0, #0x30 // RES1
> - orr x0, x0, #(1 << 0) // Non-secure EL1
> orr x0, x0, #(1 << 8) // HVC enable
> orr x0, x0, #(1 << 10) // 64-bit EL2
> msr scr_el3, x0
You also need to make sure the boot wrapper starts the kernel in S-EL1
rather than NS-EL2.
BTW, why do you need this? There are no virtualisation features
supported on the secure side.
--
Catalin
next prev parent reply other threads:[~2013-09-24 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 2:53 [Question] Verification For arm64: suspend/resume implementation Leo Yan
2013-09-13 3:04 ` Jisheng Zhang
2013-09-13 14:40 ` Lorenzo Pieralisi
2013-09-23 11:11 ` Leo Yan
2013-09-23 15:26 ` Achin Gupta
2013-09-24 2:00 ` Leo Yan
2013-09-24 9:02 ` Achin Gupta
2013-09-24 11:49 ` Leo Yan
2013-09-24 13:00 ` Catalin Marinas [this message]
2013-09-26 11:12 ` Leo Yan
2013-09-26 16:53 ` Catalin Marinas
2013-09-27 2:53 ` Leo Yan
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=20130924130012.GE25907@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).