From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
mttcg@greensocs.com, mark.burton@greensocs.com,
fred.konrad@greensocs.com
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
Subject: Re: [Qemu-devel] [RFC PATCH] target-arm/psci.c: wake up sleeping CPUs (MTTCG)
Date: Wed, 24 Jun 2015 18:01:28 +0200 [thread overview]
Message-ID: <558AD458.4000905@redhat.com> (raw)
In-Reply-To: <1435160084-938-1-git-send-email-alex.bennee@linaro.org>
On 24/06/2015 17:34, Alex Bennée wrote:
> Testing with Alexander's bare metal syncronisation tests fails in MTTCG
> leaving one CPU spinning forever waiting for the second CPU to wake up.
> We simply need to poke the halt_cond once we have processed the PSCI
> power on call.
>
> Tested-by: Alex Bennée <alex.bennee@linaro.org>
> CC: Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
>
> ---
> TODO
> - exactly how does the vexpress wake up it's sleeping CPUs?
> ---
> target-arm/psci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/target-arm/psci.c b/target-arm/psci.c
> index d8fafab..661ff28 100644
> --- a/target-arm/psci.c
> +++ b/target-arm/psci.c
> @@ -196,6 +196,8 @@ void arm_handle_psci_call(ARMCPU *cpu)
> }
> target_cpu_class->set_pc(target_cpu_state, entry);
>
> + qemu_cond_signal(target_cpu_state->halt_cond);
That's called qemu_cpu_kick(target_cpu_state). :) The patch should be
acceptable now upstream, I think.
Paolo
> ret = 0;
> break;
> case QEMU_PSCI_0_1_FN_CPU_OFF:
>
next prev parent reply other threads:[~2015-06-24 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 15:34 [Qemu-devel] [RFC PATCH] target-arm/psci.c: wake up sleeping CPUs (MTTCG) Alex Bennée
2015-06-24 16:01 ` Paolo Bonzini [this message]
2015-06-24 17:18 ` Alex Bennée
2015-06-24 17:23 ` Paolo Bonzini
2015-06-24 18:15 ` Alex Bennée
2015-06-24 19:12 ` Peter Maydell
2015-06-25 15:44 ` Andrew Jones
2015-06-26 7:06 ` Alex Bennée
2015-06-26 8:05 ` Andrew Jones
2015-06-24 23:55 ` Alexander Spyridakis
2015-06-25 6:27 ` Alex Bennée
2015-06-25 12:43 ` Frederic Konrad
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=558AD458.4000905@redhat.com \
--to=pbonzini@redhat.com \
--cc=a.spyridakis@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@greensocs.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 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).