From: Julien Grall <julien.grall@citrix.com>
To: Peng Fan <Peng.Fan@freescale.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 1/2] xen: arm: traps: check hsr.ec for ARM32
Date: Mon, 21 Sep 2015 10:47:23 +0100 [thread overview]
Message-ID: <55FFD22B.4090601@citrix.com> (raw)
In-Reply-To: <1442819224-25390-1-git-send-email-Peng.Fan@freescale.com>
Hi Peng,
On 21/09/15 08:07, Peng Fan wrote:
> To ARM64, "if ( hsr.ec >= 0x10 ) return 1;" is ok for unconditional
> check, but to ARM32, we need to use 'hsr.ec >> 30' to check.
hsr.ec is encoded on 5 bits, therefore the shift you suggest is wrong.
Maybe you wanted to use (hsr.ec >> 4)?
Although, can you explain why you need a different check for ARM32?
Regards,
> Signed-off-by: Peng Fan <Peng.Fan@freescale.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Stefano Stabellini <stefano.stabellini@citrix.com>
> Cc: Julien Grall <julien.grall@citrix.com>
> ---
> xen/arch/arm/traps.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
> index 9d2bd6a..2e2b1f2 100644
> --- a/xen/arch/arm/traps.c
> +++ b/xen/arch/arm/traps.c
> @@ -1531,8 +1531,13 @@ static int check_conditional_instr(struct cpu_user_regs *regs,
> int cond;
>
> /* Unconditional Exception classes */
> +#ifdef CONFIG_ARM_64
> if ( hsr.ec >= 0x10 )
> return 1;
> +#else
> + if ( hsr.ec >> 30 )
> + return 1;
> +#endif
>
> /* Check for valid condition in hsr */
> cond = hsr.cond.ccvalid ? hsr.cond.cc : -1;
>
--
Julien Grall
next prev parent reply other threads:[~2015-09-21 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:07 [PATCH 1/2] xen: arm: traps: check hsr.ec for ARM32 Peng Fan
2015-09-21 9:47 ` Julien Grall [this message]
2015-09-21 8:41 ` Peng Fan
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=55FFD22B.4090601@citrix.com \
--to=julien.grall@citrix.com \
--cc=Peng.Fan@freescale.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.