From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH REPOST v2] ARM: virt: fix wrong HSCTLR.EE bit setting
Date: Wed, 02 Jul 2014 15:38:36 +0100 [thread overview]
Message-ID: <53B4196C.5070007@arm.com> (raw)
In-Reply-To: <1404208910-15284-1-git-send-email-john.liuli@huawei.com>
On 01/07/14 11:01, john.liuli wrote:
> From: Li Liu <john.liuli@huawei.com>
>
> HSCTLR.EE is defined as bit[25] referring to arm manual
> DDI0606C.b(p1590).
>
> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Li Liu <john.liuli@huawei.com>
> ---
> changes v1 -> v2:
> 1)Use the canonical syntax for orr (orr r7, r7, #(1 << 25))
> 2)Use the ARM_BE8 macro instead of the open-coded CONFIG_CPU_BIG_ENDIAN
>
> arch/arm/kernel/hyp-stub.S | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/arm/kernel/hyp-stub.S b/arch/arm/kernel/hyp-stub.S
> index 797b1a6..7e666cf 100644
> --- a/arch/arm/kernel/hyp-stub.S
> +++ b/arch/arm/kernel/hyp-stub.S
> @@ -134,9 +134,7 @@ ENTRY(__hyp_stub_install_secondary)
> mcr p15, 4, r7, c1, c1, 3 @ HSTR
>
> THUMB( orr r7, #(1 << 30) ) @ HSCTLR.TE
> -#ifdef CONFIG_CPU_BIG_ENDIAN
> - orr r7, #(1 << 9) @ HSCTLR.EE
> -#endif
> +ARM_BE8(orr r7, r7, #(1 << 25)) @ HSCTLR.EE
> mcr p15, 4, r7, c1, c0, 0 @ HSCTLR
>
> mrc p15, 4, r7, c1, c1, 1 @ HDCR
>
Russell,
Assuming you're happy with this patch, would you agree to it going
through the KVM/ARM tree? We have a whole bunch of BE patches queued up,
and this is a looks like a better fix than what we have so far [1].
Thanks,
M.
[1]: https://lists.cs.columbia.edu/pipermail/kvmarm/2014-June/009950.html
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2014-07-02 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 10:01 [PATCH REPOST v2] ARM: virt: fix wrong HSCTLR.EE bit setting john.liuli
2014-07-02 14:38 ` Marc Zyngier [this message]
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=53B4196C.5070007@arm.com \
--to=marc.zyngier@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).