From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] make bh safe with hot-unplug
Date: Tue, 25 Jun 2013 08:24:28 +0200 [thread overview]
Message-ID: <51C9379C.80605@redhat.com> (raw)
In-Reply-To: <1372181916-4676-1-git-send-email-pingfank@linux.vnet.ibm.com>
Il 25/06/2013 19:38, Liu Ping Fan ha scritto:
> This series relies on refcnt of object used by bh callback to run against unplug.
>
> Open issue:
> Another choice may be rcu, but I think some issues are hard to resolve.
> Using rcu, we have two choice:
> when holding object refcnt, call qemu_bh_delete(); then after grace period, we can release.
> Or making qemu_bh_delete() sync in the path of DeviceState's finalization.
What do you mean exactly? qemu_bh_delete() is async, but it operates on
dynamically-allocated memory.
Paolo
> but currently, the callers of qemu_bh_delete() can not satisfy any of the two condition.
next prev parent reply other threads:[~2013-06-25 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:38 [Qemu-devel] [PATCH 0/3] make bh safe with hot-unplug Liu Ping Fan
2013-06-25 6:24 ` Paolo Bonzini [this message]
2013-06-25 6:32 ` liu ping fan
2013-06-25 7:53 ` Paolo Bonzini
2013-06-26 2:59 ` liu ping fan
2013-06-26 6:34 ` Paolo Bonzini
2013-06-26 8:20 ` liu ping fan
2013-06-26 8:38 ` Paolo Bonzini
2013-06-26 9:44 ` liu ping fan
2013-06-26 9:55 ` Paolo Bonzini
2013-06-27 2:08 ` liu ping fan
2013-06-27 6:59 ` Paolo Bonzini
2013-06-25 17:38 ` [Qemu-devel] [PATCH 1/3] QEMUBH: introduce canceled member for bh Liu Ping Fan
2013-06-25 17:38 ` [Qemu-devel] [PATCH 2/3] QEMUBH: pin bh's referring object while scheduling Liu Ping Fan
2013-06-25 17:38 ` [Qemu-devel] [PATCH 3/3] virtio-net: set referred object for virtio net's bh Liu Ping Fan
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=51C9379C.80605@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=stefanha@redhat.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).