Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

On 4/8/21 12:23 PM, Claudio Fontana wrote: > On 3/28/21 6:18 PM, Richard Henderson wrote: >> On 3/26/21 1:36 PM, Claudio Fontana wrote: >>> provide helper functions there to initialize 32bit models, >>> and export the a15 cpu model. >>> >>> We still need to keep around a15 until we sort out the boa

Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

On Mon, 12 Apr 2021 at 10:05, Claudio Fontana wrote: > > Hi Peter, > > On 4/8/21 12:36 PM, Peter Maydell wrote: > > On Thu, 8 Apr 2021 at 11:23, Claudio Fontana wrote: > >> Mainly for this code here a question from my side: is the current code > >> actually already "wrong"? > >> > >> I mean, we

Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

Hi Peter, On 4/8/21 12:36 PM, Peter Maydell wrote: > On Thu, 8 Apr 2021 at 11:23, Claudio Fontana wrote: >> Mainly for this code here a question from my side: is the current code >> actually already "wrong"? >> >> I mean, we unconditionally set the aarch64-capable cpu classes to all use >> aarc

Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

On Thu, 8 Apr 2021 at 11:23, Claudio Fontana wrote: > Mainly for this code here a question from my side: is the current code > actually already "wrong"? > > I mean, we unconditionally set the aarch64-capable cpu classes to all use > aarch64_gdb_arch_name and gdbstub64, > but what about an aarch6

Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

On 3/28/21 6:18 PM, Richard Henderson wrote: > On 3/26/21 1:36 PM, Claudio Fontana wrote: >> provide helper functions there to initialize 32bit models, >> and export the a15 cpu model. >> >> We still need to keep around a15 until we sort out the board configurations. >> >> cpu.c will continue to co

Re: [RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

On 3/26/21 1:36 PM, Claudio Fontana wrote: provide helper functions there to initialize 32bit models, and export the a15 cpu model. We still need to keep around a15 until we sort out the board configurations. cpu.c will continue to contain the common parts between 32 and 64. Note that we need

[RFC v12 27/65] target/arm: split a15 cpu model and 32bit class functions to cpu32.c

provide helper functions there to initialize 32bit models, and export the a15 cpu model. We still need to keep around a15 until we sort out the board configurations. cpu.c will continue to contain the common parts between 32 and 64. Note that we need to build cpu32 also for TARGET_AARCH64, becau