From: Frederic Konrad <fred.konrad@greensocs.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: mttcg@listserver.greensocs.com,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] global_mutex and multithread.
Date: Thu, 15 Jan 2015 11:41:24 +0100 [thread overview]
Message-ID: <54B79954.5010701@greensocs.com> (raw)
In-Reply-To: <CAFEAcA9NbnAinAuxzAmMRk0aiVgnTvX01qGaKO66T_Tjn+xxQw@mail.gmail.com>
On 15/01/2015 11:34, Peter Maydell wrote:
> On 15 January 2015 at 10:25, Frederic Konrad <fred.konrad@greensocs.com> wrote:
>> Hi everybody,
>>
>> In case of multithread TCG what is the best way to handle qemu_global_mutex?
> It shouldn't need any changes I think. You're basically bringing
> TCG into line with what KVM already has -- one thread per guest
> CPU; and qemu_global_mutex already works fine in that model.
>
> -- PMM
Hi Peter,
Thanks for your reply.
True that makes sense, I still think we need to synchronize vcpu when
they exit?
Fred
next prev parent reply other threads:[~2015-01-15 10:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 10:25 [Qemu-devel] global_mutex and multithread Frederic Konrad
2015-01-15 10:34 ` Peter Maydell
2015-01-15 10:41 ` Frederic Konrad [this message]
2015-01-15 10:44 ` Paolo Bonzini
2015-01-15 11:12 ` Paolo Bonzini
2015-01-15 11:14 ` Alexander Graf
2015-01-15 11:26 ` Paolo Bonzini
2015-01-15 13:30 ` Frederic Konrad
2015-01-15 13:34 ` Mark Burton
2015-01-15 12:51 ` Frederic Konrad
2015-01-15 12:56 ` Paolo Bonzini
2015-01-15 13:27 ` Frederic Konrad
2015-01-15 13:30 ` Peter Maydell
2015-01-15 19:07 ` Mark Burton
2015-01-15 20:27 ` Paolo Bonzini
2015-01-15 20:53 ` Mark Burton
2015-01-15 21:41 ` Paolo Bonzini
2015-01-15 21:41 ` Paolo Bonzini
2015-01-16 7:25 ` Mark Burton
2015-01-16 8:07 ` Jan Kiszka
2015-01-16 8:43 ` Frederic Konrad
2015-01-16 8:52 ` Mark Burton
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=54B79954.5010701@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=agraf@suse.de \
--cc=mttcg@listserver.greensocs.com \
--cc=pbonzini@redhat.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).