Re: [Qemu-devel] [PATCH 1/3] target-arm: Setup smpboot code in all setups

[Peter Maydell]

On 15 February 2011 15:02, Vincent Palatin
<address@hidden> wrote:
> This assumes that all the ARM SMP platforms are booting their
> secondary CPU the same way as the emulated Realview.
> For example, I'm currently writing a Tegra2 (dual A9) SoC emulation
> and the second CPU is halted when the platform starts and I cannot
> re-use the current smpboot firmware chunk. My current workaround is to
> use "info->nb_cpus = 1" and do the init in the board code. Forcing the
> reset function will probably not help.

My instinct here is to say "models should follow the hardware". So
if the Tegra2 SOC holds secondary cores in reset until you do something
magic to a reset controller, the model should behave the same way.
Realview boards just start all the cores at once, and that's how the
board model ought to behave.

The code in hw/arm_boot.c is really to my mind a debug convenience
for passing a bare kernel. It's a secondary thing and shouldn't drive
how we model what happens at reset.

(I'd expect that a tegra2 model would probably not use arm_boot.c;
the omap3 beagle model in meego doesn't. There's just too much
stuff that the boot ROM and the boot loader need to do to go around
emulating it all in qemu, so it's better to just pass an sd image or a
ROM image that includes the boot loader and the kernel, I think.)

-- PMM