From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] memory: unregister AddressSpace MemoryListener within BQL
Date: Wed, 11 Feb 2015 14:26:44 +0100 [thread overview]
Message-ID: <54DB5894.7090501@redhat.com> (raw)
In-Reply-To: <20150211131641.3809.42730@loki>
On 11/02/2015 14:16, Michael Roth wrote:
> Since the AddressSpace is a fields of PCIDevice, do we maybe need to make
> sure it's refcount doesn't drop to 0 prior to the RCU callback taking
> place?
Yes, but then the problem is that objects are finalized outside the big
QEMU lock.
This is a pretty large can of worms, because finalizing an object can in
turn finalize other objects, which means a lot of mutexes have to be
introduced. I'll think a bit more about it.
Paolo
prev parent reply other threads:[~2015-02-11 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 12:52 [Qemu-devel] [PATCH] memory: unregister AddressSpace MemoryListener within BQL Paolo Bonzini
2015-02-10 17:11 ` Alex Williamson
2015-02-10 17:13 ` Paolo Bonzini
2015-02-10 17:19 ` Alex Williamson
2015-02-11 5:13 ` Michael Roth
2015-02-11 7:30 ` Paolo Bonzini
2015-02-11 13:16 ` Michael Roth
2015-02-11 13:26 ` Paolo Bonzini [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=54DB5894.7090501@redhat.com \
--to=pbonzini@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).