qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: mttcg@greensocs.com, mark.burton@greensocs.com,
	a.rigo@virtualopensystems.com, qemu-devel@nongnu.org,
	guillaume.delbergue@greensocs.com, fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] [RFC PATCH V2 0/3] Multithread TCG async_safe_work part.
Date: Mon, 13 Jul 2015 16:50:32 +0100	[thread overview]
Message-ID: <87twt8jbuf.fsf@linaro.org> (raw)
In-Reply-To: <55A3A6CB.2040104@redhat.com>


Paolo Bonzini <pbonzini@redhat.com> writes:

> On 10/07/2015 18:08, fred.konrad@greensocs.com wrote:
>> From: KONRAD Frederic <fred.konrad@greensocs.com>
>> 
>> This is the async_safe_work introduction bit of the Multithread TCG work.
>> Rebased on current upstream (6169b60285fe1ff730d840a49527e721bfb30899).
>> 
>> It can be cloned here:
>> http://git.greensocs.com/fkonrad/mttcg.git branch async_work_v2
>> 
>> The first patch introduces a mutex to protect the existing queued_work_*
>> CPUState members against multiple (concurent) access.
>> 
>> The second patch introduces a tcg_executing_flag which will be 1 when we are
>> inside cpu_exec(). This is required as safe work need to be sure that's all vCPU
>> are outside cpu_exec().
>> 
>> The last patch introduces async_safe_work. It allows to add some work which will
>> be done asynchronously but only when all vCPUs are outside cpu_exec(). The tcg
>> thread will wait that no vCPUs have any pending safe work before reentering
>> cpu-exec().
>> 
>> Changes V1 -> V2:
>>   * Release the lock while running the callback for both async and safe work.
>
> What tree do these patches apply to?

See Fred's tree:

http://git.greensocs.com/fkonrad/mttcg

>
> Paolo
>
>> KONRAD Frederic (3):
>>   cpus: protect queued_work_* with work_mutex.
>>   cpus: add a tcg_executing flag.
>>   cpus: introduce async_run_safe_work_on_cpu.
>> 
>>  cpu-exec.c        |   7 +++
>>  cpus.c            | 164 +++++++++++++++++++++++++++++++++++++++++-------------
>>  include/qom/cpu.h |  28 ++++++++++
>>  qom/cpu.c         |   2 +
>>  4 files changed, 161 insertions(+), 40 deletions(-)
>> 

-- 
Alex Bennée

  reply	other threads:[~2015-07-13 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:08 [Qemu-devel] [RFC PATCH V2 0/3] Multithread TCG async_safe_work part fred.konrad
2015-07-10 16:08 ` [Qemu-devel] [RFC PATCH V2 1/3] cpus: protect queued_work_* with work_mutex fred.konrad
2015-07-10 16:08 ` [Qemu-devel] [RFC PATCH V2 2/3] cpus: add a tcg_executing flag fred.konrad
2015-07-13 15:56   ` Alex Bennée
2015-07-13 16:10     ` Peter Maydell
2015-07-13 16:15       ` Paolo Bonzini
2015-07-13 16:36         ` Alex Bennée
2015-07-15  8:40     ` Frederic Konrad
2015-07-10 16:08 ` [Qemu-devel] [RFC PATCH V2 3/3] cpus: introduce async_run_safe_work_on_cpu fred.konrad
2015-07-13 16:20   ` Alex Bennée
2015-07-13 22:56     ` Paolo Bonzini
2015-07-13 11:53 ` [Qemu-devel] [RFC PATCH V2 0/3] Multithread TCG async_safe_work part Paolo Bonzini
2015-07-13 15:50   ` Alex Bennée [this message]
2015-07-15  7:44   ` 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=87twt8jbuf.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.rigo@virtualopensystems.com \
    --cc=fred.konrad@greensocs.com \
    --cc=guillaume.delbergue@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=mttcg@greensocs.com \
    --cc=pbonzini@redhat.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).