qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v6 36/37] target-arm: Handle the CPU being in AA


From: Peter Crosthwaite
Subject: Re: [Qemu-devel] [PATCH v6 36/37] target-arm: Handle the CPU being in AArch32 mode in the AArch64 set_pc
Date: Mon, 14 Apr 2014 16:36:15 +1000

On Fri, Apr 11, 2014 at 2:15 AM, Peter Maydell <address@hidden> wrote:
> The AArch64 implementation of the set_pc method needs to be updated to
> handle the possibility that the CPU is in AArch32 mode; otherwise there
> are weird crashes when doing interprocessing in system emulation mode
> when an interrupt occurs and we fail to resynchronize the 32-bit PC
> with the TB we need to execute next.
>
> Signed-off-by: Peter Maydell <address@hidden>
> Reviewed-by: Alex Bennée <address@hidden>

Reviewed-by: Peter Crosthwaite <address@hidden>

> ---
>  target-arm/cpu64.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/target-arm/cpu64.c b/target-arm/cpu64.c
> index 9a0c431..c673ac2 100644
> --- a/target-arm/cpu64.c
> +++ b/target-arm/cpu64.c
> @@ -172,11 +172,15 @@ static void aarch64_cpu_finalizefn(Object *obj)
>  static void aarch64_cpu_set_pc(CPUState *cs, vaddr value)
>  {
>      ARMCPU *cpu = ARM_CPU(cs);
> -    /*
> -     * TODO: this will need updating for system emulation,
> -     * when the core may be in AArch32 mode.
> +    /* It's OK to look at env for the current mode here, because it's
> +     * never possible for an AArch64 TB to chain to an AArch32 TB.
> +     * (Otherwise we would need to use synchronize_from_tb instead.)
>       */
> -    cpu->env.pc = value;
> +    if (is_a64(&cpu->env)) {
> +        cpu->env.pc = value;
> +    } else {
> +        cpu->env.regs[15] = value;
> +    }
>  }
>
>  static void aarch64_cpu_class_init(ObjectClass *oc, void *data)
> --
> 1.9.1
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]