From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com
Subject: [Qemu-devel] [PULL 2/8] memory: Sanity check that no listeners remain on a destroyed AddressSpace
Date: Mon, 02 Jun 2014 16:00:27 -0600 [thread overview]
Message-ID: <20140602220026.26111.28290.stgit@bling.home> (raw)
In-Reply-To: <20140602215946.26111.16417.stgit@bling.home>
From: David Gibson <david@gibson.dropbear.id.au>
At the moment, most AddressSpace objects last as long as the guest system
in practice, but that could well change in future. In addition, for VFIO
we will be introducing some private per-AdressSpace information, which must
be disposed of before the AddressSpace itself is destroyed.
To reduce the chances of subtle bugs in this area, this patch adds
asssertions to ensure that when an AddressSpace is destroyed, there are no
remaining MemoryListeners using that AS as a filter.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
memory.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/memory.c b/memory.c
index 3f1df23..678661e 100644
--- a/memory.c
+++ b/memory.c
@@ -1722,12 +1722,19 @@ void address_space_init(AddressSpace *as, MemoryRegion *root, const char *name)
void address_space_destroy(AddressSpace *as)
{
+ MemoryListener *listener;
+
/* Flush out anything from MemoryListeners listening in on this */
memory_region_transaction_begin();
as->root = NULL;
memory_region_transaction_commit();
QTAILQ_REMOVE(&address_spaces, as, address_spaces_link);
address_space_destroy_dispatch(as);
+
+ QTAILQ_FOREACH(listener, &memory_listeners, link) {
+ assert(listener->address_space_filter != as);
+ }
+
flatview_unref(as->current_map);
g_free(as->name);
g_free(as->ioeventfds);
next prev parent reply other threads:[~2014-06-02 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 22:00 [Qemu-devel] [PULL 0/8] Series short description Alex Williamson
2014-06-02 22:00 ` [Qemu-devel] [PULL 1/8] vfio-pci: Quirk RTL8168 NIC Alex Williamson
2014-06-02 22:00 ` Alex Williamson [this message]
2014-06-02 22:00 ` [Qemu-devel] [PULL 3/8] int128: Add int128_exts64() Alex Williamson
2014-06-02 22:00 ` [Qemu-devel] [PULL 4/8] vfio: Fix 128 bit handling Alex Williamson
2014-06-02 22:00 ` [Qemu-devel] [PULL 5/8] vfio: Rework to have error paths Alex Williamson
2014-06-02 22:00 ` [Qemu-devel] [PULL 6/8] vfio: Introduce VFIO address spaces Alex Williamson
2014-06-02 22:00 ` [Qemu-devel] [PULL 7/8] vfio: Create VFIOAddressSpace objects as needed Alex Williamson
2014-06-02 22:01 ` [Qemu-devel] [PULL 8/8] vfio: Add guest side IOMMU support Alex Williamson
2014-06-02 22:09 ` [Qemu-devel] [PULL 0/8] Series short description Alex Williamson
2014-06-03 14:34 ` Peter Maydell
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=20140602220026.26111.28290.stgit@bling.home \
--to=alex.williamson@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).