From: Denis Plotnikov <den-plotnikov@yandex-team.ru>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, dgilbert@redhat.com, yc-core@yandex-team.ru,
armbru@redhat.com
Subject: [PING][Ping] [PATCH v1 0/2] vl: flush all task from rcu queue before exiting
Date: Thu, 25 Nov 2021 10:09:21 +0300 [thread overview]
Message-ID: <9c80d44e-3d51-7209-d037-e96deb4ca2bc@yandex-team.ru> (raw)
In-Reply-To: <6d2b4b4f-707f-9d5b-7ffe-c6d8d05ffb06@yandex-team.ru>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
ping ping
On 19.11.2021 12:42, Denis Plotnikov wrote:
>
> Ping!
>
> On 15.11.2021 12:41, Denis Plotnikov wrote:
>> v1 -> v0:
>> * move monitor cleanup to the very end of qemu cleanup [Paolo]
>>
>> The goal is to notify management layer about device destruction on qemu shutdown.
>> Without this series DEVICE_DELETED event may not be sent because of stuck tasks
>> in the rcu thread. The rcu tasks may stuck on qemu shutdown because the rcu
>> not always have enough time to run them.
>>
>>
>> Denis Plotnikov (2):
>> monitor: move monitor destruction to the very end of qemu cleanup
>> vl: flush all task from rcu queue before exiting
>>
>> include/qemu/rcu.h | 1 +
>> monitor/monitor.c | 6 ++++++
>> softmmu/runstate.c | 4 +++-
>> util/rcu.c | 12 ++++++++++++
>> 4 files changed, 22 insertions(+), 1 deletion(-)
>>
[-- Attachment #2: Type: text/html, Size: 1535 bytes --]
prev parent reply other threads:[~2021-11-25 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 9:41 [PATCH v1 0/2] vl: flush all task from rcu queue before exiting Denis Plotnikov
2021-11-15 9:41 ` [PATCH v1 1/2] monitor: move monitor destruction to the very end of qemu cleanup Denis Plotnikov
2021-11-25 9:26 ` Markus Armbruster
2021-11-15 9:41 ` [PATCH v1 2/2] vl: flush all task from rcu queue before exiting Denis Plotnikov
2021-11-19 9:42 ` [Ping] [PATCH v1 0/2] " Denis Plotnikov
2021-11-25 7:09 ` Denis Plotnikov [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=9c80d44e-3d51-7209-d037-e96deb4ca2bc@yandex-team.ru \
--to=den-plotnikov@yandex-team.ru \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yc-core@yandex-team.ru \
/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).