From: Paolo Bonzini <pbonzini@redhat.com>
To: Denis Plotnikov <den-plotnikov@yandex-team.ru>, qemu-devel@nongnu.org
Cc: yc-core@yandex-team.ru, mlevitsk@redhat.com
Subject: Re: [Ping][PATCH v0] vl: flush all task from rcu queue before exiting
Date: Tue, 9 Nov 2021 18:46:20 +0100 [thread overview]
Message-ID: <5830d625-de03-7dc7-c662-e434ebeaa651@redhat.com> (raw)
In-Reply-To: <96bfe630-fb3d-2ac8-60b8-ae23ed7b3742@yandex-team.ru>
On 11/9/21 08:23, Denis Plotnikov wrote:
> Ping ping!
Looks good, but can you explain why it's okay to call it before
qemu_chr_cleanup() and user_creatable_cleanup()?
I think a better solution to the ordering problem would be:
qemu_chr_cleanup();
user_creatable_cleanup();
flush_rcu();
monitor_cleanup();
with something like this:
diff --git a/chardev/char-fe.c b/chardev/char-fe.c
index 7789f7be9c..f0c3ea5447 100644
--- a/chardev/char-fe.c
+++ b/chardev/char-fe.c
@@ -195,6 +195,7 @@ bool qemu_chr_fe_init(CharBackend *b,
int tag = 0;
if (s) {
+ object_ref(OBJECT(s));
if (CHARDEV_IS_MUX(s)) {
MuxChardev *d = MUX_CHARDEV(s);
@@ -241,6 +242,7 @@ void qemu_chr_fe_deinit(CharBackend *b, bool del)
} else {
object_unref(obj);
}
+ object_unref(obj);
}
b->chr = NULL;
}
to keep the chardev live between qemu_chr_cleanup() and monitor_cleanup().
Paolo
next prev parent reply other threads:[~2021-11-09 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 13:39 [PATCH v0] vl: flush all task from rcu queue before exiting Denis Plotnikov
2021-11-02 14:13 ` Denis Plotnikov
2021-11-09 7:23 ` [Ping][PATCH " Denis Plotnikov
2021-11-09 17:46 ` Paolo Bonzini [this message]
2021-11-10 13:29 ` Denis Plotnikov
2021-11-10 16:29 ` Paolo Bonzini
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=5830d625-de03-7dc7-c662-e434ebeaa651@redhat.com \
--to=pbonzini@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=mlevitsk@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).