From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: Vincent Palatin <vincent.palatin_qemu@polytechnique.org>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] target-arm: Setup smpboot code in all setups
Date: Tue, 15 Feb 2011 18:25:58 +0100 [thread overview]
Message-ID: <20110215172558.GJ19666@os.inf.tu-dresden.de> (raw)
In-Reply-To: <AANLkTikd+dbzhnV30YkrocDo-1htmFzCqsp0Xpdo8D1N@mail.gmail.com>
Hi,
On Tue Feb 15, 2011 at 10:02:05 -0500, Vincent Palatin wrote:
> >> Moving in the right direction, but it would be cleaner if the secondary
> >> CPU reset was handled inside arm_boot.c, I think (there is a TODO
> >> in that file to that effect). Then we could get rid of the cpu reset
> >> hook from realview.c.
> >
> > Like the following?
>
> 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.
The smpboot code also halts the CPUs, i.e. they are waiting in wfi.
What would you like to have instead? Maybe it's not so different...
Adam
--
Adam adam@os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
next prev parent reply other threads:[~2011-02-15 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 10:48 [Qemu-devel] [PATCH 1/3] target-arm: Setup smpboot code in all setups Adam Lackorzynski
2011-02-15 13:01 ` Peter Maydell
2011-02-15 13:12 ` Adam Lackorzynski
2011-02-15 13:37 ` Peter Maydell
2011-02-15 14:30 ` Adam Lackorzynski
2011-02-15 15:02 ` Vincent Palatin
2011-02-15 17:25 ` Adam Lackorzynski [this message]
2011-02-15 17:46 ` 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=20110215172558.GJ19666@os.inf.tu-dresden.de \
--to=adam@os.inf.tu-dresden.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vincent.palatin_qemu@polytechnique.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).