All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: vijay.kilari@gmail.com, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, stefano.stabellini@citrix.com,
	xen-devel@lists.xen.org
Cc: Prasun.Kapoor@caviumnetworks.com, vijaya.kumar@caviumnetworks.com
Subject: Re: [PATCH] xen/arm: Restricted access to IFSR32_EL2 and FPEXC32_EL2
Date: Tue, 27 May 2014 12:21:31 +0100	[thread overview]
Message-ID: <5384753B.7040904@linaro.org> (raw)
In-Reply-To: <1401187022-15822-1-git-send-email-vijay.kilari@gmail.com>

Hi Vijaya,

On 05/27/2014 11:37 AM, vijay.kilari@gmail.com wrote:
> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> 
> Some platforms does not support aarch32 mode. So access only if
> platform supports it. Accessing these registers will
> raise exception
> 
> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> ---
>  xen/arch/arm/arm64/vfp.c |    6 ++++--
>  xen/arch/arm/traps.c     |    7 +++++--
>  2 files changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/xen/arch/arm/arm64/vfp.c b/xen/arch/arm/arm64/vfp.c
> index 3cd2b1b..c550a68 100644
> --- a/xen/arch/arm/arm64/vfp.c
> +++ b/xen/arch/arm/arm64/vfp.c
> @@ -28,7 +28,8 @@ void vfp_save_state(struct vcpu *v)
>  
>      v->arch.vfp.fpsr = READ_SYSREG32(FPSR);
>      v->arch.vfp.fpcr = READ_SYSREG32(FPCR);
> -    v->arch.vfp.fpexc32_el2 = READ_SYSREG32(FPEXC32_EL2);
> +    if ( cpu_has_el2_32 )

You should use is_32bit_domain here. If your platform doesn't support
aarch32 mode, then we should not create 32bit domain.

I think you will have to deny somewhere the domain creation in this case.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-05-27 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 10:37 [PATCH] xen/arm: Restricted access to IFSR32_EL2 and FPEXC32_EL2 vijay.kilari
2014-05-27 11:21 ` Julien Grall [this message]
2014-09-17  8:59   ` Vijay Kilari
2014-09-17 17:00     ` 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=5384753B.7040904@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=vijay.kilari@gmail.com \
    --cc=vijaya.kumar@caviumnetworks.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.