From: Avi Kivity <avi@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: bill4carson@gmail.com, qemu-devel@nongnu.org,
android-virt@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH] Add minimal Vexpress Cortex A15 support
Date: Tue, 06 Dec 2011 14:39:16 +0200 [thread overview]
Message-ID: <4EDE0CF4.4070503@redhat.com> (raw)
In-Reply-To: <CAFEAcA-0F5q5=mYLpnbz1Mu2s-=XqECvr5rY1U-TaS0LtRLrfg@mail.gmail.com>
On 12/06/2011 02:35 PM, Peter Maydell wrote:
> On 6 December 2011 12:28, Avi Kivity <avi@redhat.com> wrote:
> > On 12/01/2011 03:37 AM, bill4carson@gmail.com wrote:
> >> + /* ??? Hack to map an additional page of ram for the secondary CPU
> >> + startup code. I guess this works on real hardware because the
> >> + BootROM happens to be in ROM/flash or in memory that isn't clobbered
> >> + until after Linux boots the secondary CPUs. */
> >> + ram_offset = qemu_ram_alloc(NULL, "vexpress.hack", 0x1000);
> >> + cpu_register_physical_memory(SMP_BOOT_ADDR, 0x1000,
> >> + ram_offset | IO_MEM_RAM);
>
> > It would be better to unhack this; short-term hacks tend to remain in
> > the long term, and even after they're fixed we keep them for backwards
> > compatibility.
>
> Do you have a better suggestion in this case? We've had the same
> code in the realview board since 2007 when ARM SMP support was first
> added...
No idea really since I don't fully understand what's going on. It's
just a knee-jerk reaction to the word 'hack'.
Can't we just do what real hardware does?
> There's no particular back-compat implication here as far as I know:
> the location of the secondary CPU holding pen code is irrelevant to
> the actual guest being run. (On a real system it will be somewhere
> inside the boot ROM.)
Suppose you live migrate when the code is running there?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-06 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 1:37 [Qemu-devel] Add minimal support for Cortex A15 for ARM KVM bill4carson
2011-12-01 1:37 ` [Qemu-devel] [PATCH] Add minimal Vexpress Cortex A15 support bill4carson
2011-12-01 11:29 ` Peter Maydell
2011-12-01 11:35 ` Peter Maydell
2011-12-05 17:59 ` Andreas Färber
2011-12-05 18:30 ` Peter Maydell
2011-12-06 12:28 ` Avi Kivity
2011-12-06 12:35 ` Peter Maydell
2011-12-06 12:39 ` Avi Kivity [this message]
2011-12-06 12:48 ` Peter Maydell
2011-12-06 13:12 ` Avi Kivity
2011-12-06 13:17 ` Peter Maydell
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=4EDE0CF4.4070503@redhat.com \
--to=avi@redhat.com \
--cc=android-virt@lists.cs.columbia.edu \
--cc=bill4carson@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.