From: Paolo Bonzini <pbonzini@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH] cpus: run work items for all vCPUs if single-threaded
Date: Fri, 16 Nov 2018 00:15:53 +0100 [thread overview]
Message-ID: <7648aa01-5458-bef1-9b65-f6ef83287e63@redhat.com> (raw)
In-Reply-To: <20181114194208.GA500@flamenco>
On 14/11/2018 20:42, Emilio G. Cota wrote:
> On Wed, Nov 14, 2018 at 12:44:00 +0100, Paolo Bonzini wrote:
>> This avoids the following deadlock:
>>
>> 1) a thread calls run_on_cpu for CPU 2 from a timer, and single_tcg_halt_cond
>> is signaled
>>
>> 2) CPU 1 is running and exits. It finds no work item and enters CPU 2
>>
>> 3) because the I/O thread is stuck in run_on_cpu, the round-robin kick
>> timer never triggers, and CPU 2 never runs the work item
>>
>> 4) run_on_cpu never completes
>
> I'm having trouble understanding (2)->(3).
>
> When the vCPU thread enters CPU 2, shouldn't it detect that work is
> pending? As in:
>
> /* assume cpu == cpu2 in the example above */
> while (cpu && !cpu->queued_work_first && !cpu->exit_request) {
>
> Both cpu->queued_work_first and cpu->exit_request will be set for cpu2.
>
> I can see though how with an additional CPU the deadlock
> could happen. For example, the I/O thread does run_on_cpu(cpu3),
> which kicks cpu1 (i.e. the tcg_current_rr_cpu) and cpu3, but not cpu2.
> Then cpu1 exits, and cpu2 starts executing; unless cpu2 exits on its
> own volition, it will run forever.
Yes, the thread must call run_on_cpu for CPU *3* from a timer.
Paolo
next prev parent reply other threads:[~2018-11-15 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:44 [Qemu-devel] [PATCH] cpus: run work items for all vCPUs if single-threaded Paolo Bonzini
2018-11-14 19:42 ` Emilio G. Cota
2018-11-15 23:15 ` Paolo Bonzini [this message]
2018-11-15 23:50 ` Emilio G. Cota
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=7648aa01-5458-bef1-9b65-f6ef83287e63@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=dgilbert@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).