From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: mttcg@listserver.greensocs.com,
"Alexander Spyridakis" <a.spyridakis@virtualopensystems.com>,
"Mark Burton" <mark.burton@greensocs.com>,
"Alvise Rigo" <a.rigo@virtualopensystems.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] TCG baremetal tests repo
Date: Wed, 24 Jun 2015 20:09:06 +0100 [thread overview]
Message-ID: <CAFEAcA_Pigi3xjKFmQam2gjBA-iMSbC12uA16+Pt-3V8hVFidg@mail.gmail.com> (raw)
In-Reply-To: <871th1ysa8.fsf@linaro.org>
On 24 June 2015 at 17:39, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> Alexander Spyridakis <a.spyridakis@virtualopensystems.com> writes:
>> You can find the latest tcg atomic test payload in the following repo:
>>> git clone https://git.virtualopensystems.com/dev/tcg_baremetal_tests.git
>>
>> You also need an arm baremetal cross-compiler like arm-none-gnueabi- (arm)
>> and the usual aarch64-linux-gnu- (arm64). Due to a PSCI bug in the current
>> multithreading tcg repo, the atomic test was modified to work also on the
>> vexpress machine model.
>
> I sent a patch to fix the PSCI hang case to wake up the sleeping CPU. I
> couldn't figure out how the vexpress code was waking it's CPUs. Do they
> just start powered on?
Yes -- our vexpress model is "like hardware", so all CPUs leap into
the boot firmware at once, and the firmware deals with putting the
secondaries into a pen to be released in a controlled manner later.
[assuming you're not using -kernel; if you are then boot.c has the
secondary pen code]
-- PMM
next prev parent reply other threads:[~2015-06-24 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 10:54 [Qemu-devel] TCG baremetal tests repo Alexander Spyridakis
2015-06-22 12:59 ` Alex Bennée
2015-06-24 16:39 ` Alex Bennée
2015-06-24 19:09 ` Peter Maydell [this message]
2015-06-25 6:39 ` Alex Bennée
2015-06-25 16:01 ` Frederic Konrad
2015-06-26 0:26 ` Alexander Spyridakis
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=CAFEAcA_Pigi3xjKFmQam2gjBA-iMSbC12uA16+Pt-3V8hVFidg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=a.rigo@virtualopensystems.com \
--cc=a.spyridakis@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--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 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).