From: Paolo Bonzini <pbonzini@redhat.com>
To: alvise rigo <a.rigo@virtualopensystems.com>
Cc: mttcg@listserver.greensocs.com,
"Claudio Fontana" <claudio.fontana@huawei.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Jani Kokkonen" <jani.kokkonen@huawei.com>,
"VirtualOpenSystems Technical Team" <tech@virtualopensystems.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RFC v3 09/13] cpus.c: introduce simple callback support
Date: Fri, 10 Jul 2015 12:24:12 +0200 [thread overview]
Message-ID: <559F9D4C.3050703@redhat.com> (raw)
In-Reply-To: <CAH47eN3u-5ni8t_bGOm5DXNgVPNduBJ_WGguNVX7b8XaW+R8Kw@mail.gmail.com>
On 10/07/2015 11:47, alvise rigo wrote:
> I tried to use it, but it would then create a deadlock at a very early
> stage of the stress test.
> The problem is likely related to the fact that flush_queued_work
> happens with the global mutex locked.
Let's fix that and move the global mutex inside the callbacks. I can
take a look.
Paolo
> As Frederick suggested, we can use the newly introduced
> flush_queued_safe_work for this.
>
> Regards,
> alvise
>
> On Fri, Jul 10, 2015 at 11:36 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>
>> On 10/07/2015 10:23, Alvise Rigo wrote:
>>> In order to perfom "lazy" TLB invalidation requests, introduce a
>>> queue of callbacks at every vCPU disposal that will be fired just
>>> before entering the next TB.
>>>
>>> Suggested-by: Jani Kokkonen <jani.kokkonen@huawei.com>
>>> Suggested-by: Claudio Fontana <claudio.fontana@huawei.com>
>>> Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
>>
>> Why is async_run_on_cpu not enough?
>>
>> Paolo
>>
>>> ---
>>> cpus.c | 34 ++++++++++++++++++++++++++++++++++
>>> exec.c | 1 +
>>> include/qom/cpu.h | 20 ++++++++++++++++++++
>>> 3 files changed, 55 insertions(+)
>>>
>>> diff --git a/cpus.c b/cpus.c
>>> index f4d938e..b9f0329 100644
>>> --- a/cpus.c
>>> +++ b/cpus.c
>>> @@ -1421,6 +1421,7 @@ static int tcg_cpu_exec(CPUArchState *env)
>>> cpu->icount_extra = count;
>>> }
>>> qemu_mutex_unlock_iothread();
>>> + cpu_exit_callbacks_call_all(cpu);
>>> ret = cpu_exec(env);
>>> cpu->tcg_executing = 0;
>>>
>>> @@ -1469,6 +1470,39 @@ static void tcg_exec_all(CPUState *cpu)
>>> cpu->exit_request = 0;
>>> }
>>>
>>> +void cpu_exit_callback_add(CPUState *cpu, CPUExitCallback callback,
>>> + void *opaque)
>>> +{
>>> + CPUExitCB *cb;
>>> +
>>> + cb = g_malloc(sizeof(*cb));
>>> + cb->callback = callback;
>>> + cb->opaque = opaque;
>>> +
>>> + qemu_mutex_lock(&cpu->exit_cbs.mutex);
>>> + QTAILQ_INSERT_TAIL(&cpu->exit_cbs.exit_callbacks, cb, entry);
>>> + qemu_mutex_unlock(&cpu->exit_cbs.mutex);
>>> +}
>>> +
>>> +void cpu_exit_callbacks_call_all(CPUState *cpu)
>>> +{
>>> + CPUExitCB *cb, *next;
>>> +
>>> + if (QTAILQ_EMPTY(&cpu->exit_cbs.exit_callbacks)) {
>>> + return;
>>> + }
>>> +
>>> + QTAILQ_FOREACH_SAFE(cb, &cpu->exit_cbs.exit_callbacks, entry, next) {
>>> + cb->callback(cpu, cb->opaque);
>>> +
>>> + /* one-shot callbacks, remove it after using it */
>>> + qemu_mutex_lock(&cpu->exit_cbs.mutex);
>>> + QTAILQ_REMOVE(&cpu->exit_cbs.exit_callbacks, cb, entry);
>>> + g_free(cb);
>>> + qemu_mutex_unlock(&cpu->exit_cbs.mutex);
>>> + }
>>> +}
>>> +
>>> void list_cpus(FILE *f, fprintf_function cpu_fprintf, const char *optarg)
>>> {
>>> /* XXX: implement xxx_cpu_list for targets that still miss it */
>>> diff --git a/exec.c b/exec.c
>>> index 51958ed..322f2c6 100644
>>> --- a/exec.c
>>> +++ b/exec.c
>>> @@ -531,6 +531,7 @@ void cpu_exec_init(CPUArchState *env)
>>> cpu->numa_node = 0;
>>> QTAILQ_INIT(&cpu->breakpoints);
>>> QTAILQ_INIT(&cpu->watchpoints);
>>> + QTAILQ_INIT(&cpu->exit_cbs.exit_callbacks);
>>> #ifndef CONFIG_USER_ONLY
>>> cpu->as = &address_space_memory;
>>> cpu->thread_id = qemu_get_thread_id();
>>> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
>>> index 8d121b3..0ec020b 100644
>>> --- a/include/qom/cpu.h
>>> +++ b/include/qom/cpu.h
>>> @@ -201,6 +201,24 @@ typedef struct CPUWatchpoint {
>>> QTAILQ_ENTRY(CPUWatchpoint) entry;
>>> } CPUWatchpoint;
>>>
>>> +/* vCPU exit callbacks */
>>> +typedef void (*CPUExitCallback)(CPUState *cpu, void *opaque);
>>> +struct CPUExitCBs {
>>> + QemuMutex mutex;
>>> + QTAILQ_HEAD(exit_callbacks_head, CPUExitCB) exit_callbacks;
>>> +};
>>> +
>>> +typedef struct CPUExitCB {
>>> + CPUExitCallback callback;
>>> + void *opaque;
>>> +
>>> + QTAILQ_ENTRY(CPUExitCB) entry;
>>> +} CPUExitCB;
>>> +
>>> +void cpu_exit_callback_add(CPUState *cpu, CPUExitCallback callback,
>>> + void *opaque);
>>> +void cpu_exit_callbacks_call_all(CPUState *cpu);
>>> +
>>> /* Rendezvous support */
>>> #define TCG_RDV_POLLING_PERIOD 10
>>> typedef struct CpuExitRendezvous {
>>> @@ -305,6 +323,8 @@ struct CPUState {
>>>
>>> void *opaque;
>>>
>>> + /* One-shot callbacks for stopping requests. */
>>> + struct CPUExitCBs exit_cbs;
>>> volatile int pending_rdv;
>>>
>>> /* In order to avoid passing too many arguments to the MMIO helpers,
>>>
>
>
next prev parent reply other threads:[~2015-07-10 10:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 8:23 [Qemu-devel] [RFC v3 00/13] Slow-path for atomic instruction translation Alvise Rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 01/13] exec: Add new exclusive bitmap to ram_list Alvise Rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 02/13] cputlb: Add new TLB_EXCL flag Alvise Rigo
2015-07-16 14:32 ` Alex Bennée
2015-07-16 15:04 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 03/13] softmmu: Add helpers for a new slow-path Alvise Rigo
2015-07-16 14:53 ` Alex Bennée
2015-07-16 15:15 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 04/13] tcg-op: create new TCG qemu_ldlink and qemu_stcond instructions Alvise Rigo
2015-07-17 9:49 ` Alex Bennée
2015-07-17 10:05 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 05/13] target-arm: translate: implement qemu_ldlink and qemu_stcond ops Alvise Rigo
2015-07-17 12:51 ` Alex Bennée
2015-07-17 13:01 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 06/13] target-i386: " Alvise Rigo
2015-07-17 12:56 ` Alex Bennée
2015-07-17 13:27 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 07/13] ram_addr.h: Make exclusive bitmap accessors atomic Alvise Rigo
2015-07-17 13:32 ` Alex Bennée
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 08/13] exec.c: introduce a simple rendezvous support Alvise Rigo
2015-07-17 13:45 ` Alex Bennée
2015-07-17 13:54 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 09/13] cpus.c: introduce simple callback support Alvise Rigo
2015-07-10 9:36 ` Paolo Bonzini
2015-07-10 9:47 ` alvise rigo
2015-07-10 9:53 ` Frederic Konrad
2015-07-10 10:06 ` alvise rigo
2015-07-10 10:24 ` Paolo Bonzini [this message]
2015-07-10 12:16 ` Frederic Konrad
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 10/13] Simple TLB flush wrap to use as exit callback Alvise Rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 11/13] Introduce exit_flush_req and tcg_excl_access_lock Alvise Rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 12/13] softmmu_llsc_template.h: move to multithreading Alvise Rigo
2015-07-17 15:27 ` Alex Bennée
2015-07-17 15:31 ` alvise rigo
2015-07-10 8:23 ` [Qemu-devel] [RFC v3 13/13] softmmu_template.h: " Alvise Rigo
2015-07-17 15:57 ` Alex Bennée
2015-07-17 16:19 ` alvise rigo
2015-07-10 8:31 ` [Qemu-devel] [RFC v3 00/13] Slow-path for atomic instruction translation Mark Burton
2015-07-10 8:58 ` alvise rigo
2015-07-10 8:39 ` Frederic Konrad
2015-07-10 9:04 ` alvise rigo
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=559F9D4C.3050703@redhat.com \
--to=pbonzini@redhat.com \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=jani.kokkonen@huawei.com \
--cc=mttcg@listserver.greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
/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).