qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [Bug 1821430] Re: qemu-user-arm (4.0.0-rc0) crashes


From: Richard Henderson
Subject: Re: [Qemu-devel] [Bug 1821430] Re: qemu-user-arm (4.0.0-rc0) crashes
Date: Mon, 25 Mar 2019 08:39:12 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1

On 3/25/19 8:25 AM, Alex Bennée wrote:
> 
> Peter Maydell <address@hidden> writes:
> 
>> On Mon, 25 Mar 2019 at 13:29, Alex Bennée <address@hidden> wrote:
>>> I was going to suggest -cpu cortex-a53,aarch64=off but that seems to be
>>> only for KVM guests.
>>>
>>> Is there actually a v8 A profile 32 bit only CPU part?
>>
>> You can for instance connect up a Cortex-A53 with the
>> AA64nAA32 config signals hardwired to 0 ("go into AArch32
>> on power-on-reset"), which is functionally the same thing.
> 
> So would it be reasonable to have a
> 
> #ifndef TARGET_AARCH64
>     { .name = "cortex-a53 (32bit)",         .initfn = aarch32_a53_initfn },
> #endif
> 
> and the appropriate init function in cpu.c? That should be all we need right?

Perhaps, but as I mention up-thread there's a 2-line fix to arm_max_initfn that
will be sufficient for CONFIG_USER_ONLY.  I think that's the safer option for 
4.0.


r~




reply via email to

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