From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: hyp: boot secondary CPUs through the right entry point
Date: Mon, 7 Jan 2013 12:26:44 +0000 [thread overview]
Message-ID: <20130107122644.GB2050@linaro.org> (raw)
In-Reply-To: <1357321455-9264-2-git-send-email-marc.zyngier@arm.com>
On Fri, Jan 04, 2013 at 05:44:14PM +0000, Marc Zyngier wrote:
> Secondary CPUs should use the __hyp_stub_install_secondary entry
> point, so boot mode inconsistencies can be detected.
>
> Reported-by: Ian Molton <ian.molton@collabora.co.uk>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
I was just going to report this, but I see I was beaten to it...
Acked-by: Dave Martin <dave.martin@linaro.org>
Cheers
---Dave
> ---
> arch/arm/kernel/head.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/kernel/head.S b/arch/arm/kernel/head.S
> index 4eee351..16abc83 100644
> --- a/arch/arm/kernel/head.S
> +++ b/arch/arm/kernel/head.S
> @@ -331,7 +331,7 @@ ENTRY(secondary_startup)
> * as it has already been validated by the primary processor.
> */
> #ifdef CONFIG_ARM_VIRT_EXT
> - bl __hyp_stub_install
> + bl __hyp_stub_install_secondary
> #endif
> safe_svcmode_maskall r9
>
> --
> 1.8.1
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-01-07 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 17:44 [PATCH 0/2] HYP boot mode fixes Marc Zyngier
2013-01-04 17:44 ` [PATCH 1/2] ARM: hyp: boot secondary CPUs through the right entry point Marc Zyngier
2013-01-07 12:26 ` Dave Martin [this message]
2013-01-04 17:44 ` [PATCH 2/2] ARM: hyp: simplify __hyp_stub_install epilog Marc Zyngier
2013-01-07 12:18 ` Dave Martin
2013-01-07 13:27 ` Marc Zyngier
2013-01-07 13:49 ` Dave Martin
2013-01-09 14:46 ` [PATCH 0/2] HYP boot mode fixes Will Deacon
2013-01-09 14:48 ` Marc Zyngier
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=20130107122644.GB2050@linaro.org \
--to=dave.martin@linaro.org \
--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).