From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alistair Francis" <alistair.francis@xilinx.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MTTCG External Halt
Date: Tue, 30 Jan 2018 23:26:00 -0500 [thread overview]
Message-ID: <0b0a9968-02bf-9273-e5fe-a69e04cf7f5e@redhat.com> (raw)
In-Reply-To: <CAKmqyKMopCi5jaDstAX0Q3CzLdQ9wRgKWT2ggR_Or8Yh09zkrQ@mail.gmail.com>
On 30/01/2018 18:56, Alistair Francis wrote:
>
> I don't have a good solution though, as setting CPU_INTERRUPT_RESET
> doesn't help (that isn't handled while we are halted) and
> async_run_on_cpu()/run_on_cpu() doesn't reliably reset the CPU when we
> want.
>
> I've ever tried pausing all CPUs before reseting the CPU and them
> resuming them all but that doesn't seem to to work either.
async_safe_run_on_cpu would be like async_run_on_cpu, except that it
takes care of stopping all other CPUs while the function runs.
> Is there
> anything I'm missing? Is there no reliable way to reset a CPU?
What do you mean by reliable? Executing no instruction after the one
you were at?
Paolo
next prev parent reply other threads:[~2018-01-31 4:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 22:10 [Qemu-devel] MTTCG External Halt Alistair Francis
2018-01-03 22:14 ` Peter Maydell
2018-01-03 22:23 ` Alistair Francis
2018-01-04 1:14 ` Alistair Francis
2018-01-04 11:08 ` Alex Bennée
2018-01-06 2:23 ` Alistair Francis
2018-01-30 23:56 ` Alistair Francis
2018-01-31 4:26 ` Paolo Bonzini [this message]
2018-01-31 16:08 ` Alistair Francis
2018-01-31 20:32 ` Alex Bennée
2018-01-31 22:31 ` Alistair Francis
2018-02-01 12:01 ` Alex Bennée
2018-02-01 17:13 ` Alistair Francis
2018-02-01 21:00 ` Alistair Francis
2018-02-02 20:37 ` Alex Bennée
2018-02-02 21:49 ` Alistair Francis
2018-02-02 21:59 ` Alistair Francis
2018-04-22 23:03 ` Philippe Mathieu-Daudé
2018-01-31 17:13 ` Paolo Bonzini
2018-01-31 18:17 ` Alistair Francis
2018-01-31 18:48 ` Peter Maydell
2018-01-31 18:51 ` Alistair Francis
2018-01-31 18:56 ` Alistair Francis
2018-01-31 18:59 ` Peter Maydell
2018-01-31 19:37 ` Alistair Francis
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=0b0a9968-02bf-9273-e5fe-a69e04cf7f5e@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@xilinx.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).