From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Use per-cpu reset handlers.
Date: Mon, 30 Nov 2009 18:34:33 +0200 [thread overview]
Message-ID: <4B13F419.7020306@redhat.com> (raw)
In-Reply-To: <5d6222a80911300800o6aa548f0r88edd8e1e66e758e@mail.gmail.com>
On 11/30/2009 06:00 PM, Glauber Costa wrote:
> The proposal in this patch is to add a system_reset caller that only
> resets state related to the cpu. This will guarantee that does functions
> are called from the cpu-threads, not the I/O thread.
>
> In principle, it might seem close to the remote execution mechanism, but:
> * It does not involve any extra signalling, so it should be faster.
> * The cpu is guaranteed to be stopped, so it is much less racy.
> * What runs where becomes more explicit.
> * This is much, much less racy
>
> The previous implementation was giving me races on reset. This one makes
> it work flawlesly w.r.t reset.
>
Looks pretty good.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-11-30 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 16:00 [Qemu-devel] Use per-cpu reset handlers Glauber Costa
2009-11-30 16:34 ` Avi Kivity [this message]
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=4B13F419.7020306@redhat.com \
--to=avi@redhat.com \
--cc=glommer@gmail.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).