From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH v6 1/7] memory: Sanity check that no listeners remain on a destroyed AddressSpace
Date: Fri, 23 May 2014 14:59:14 +1000 [thread overview]
Message-ID: <1400821160-25258-2-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1400821160-25258-1-git-send-email-aik@ozlabs.ru>
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>
---
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);
--
1.9.rc0
next prev parent reply other threads:[~2014-05-23 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 4:59 [Qemu-devel] [PATCH v6 0/7] vfio: Prepare for SPAPR Alexey Kardashevskiy
2014-05-23 4:59 ` Alexey Kardashevskiy [this message]
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 2/7] int128: Add int128_exts64() Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 3/7] vfio: Fix 128 bit handling Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 4/7] vfio: Rework to have error paths Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 5/7] vfio: Introduce VFIO address spaces Alexey Kardashevskiy
2014-05-23 11:28 ` Alexander Graf
2014-05-23 12:03 ` Alexey Kardashevskiy
2014-05-23 12:05 ` Alexander Graf
2014-05-23 16:16 ` Alexey Kardashevskiy
2014-05-23 21:15 ` Alexander Graf
2014-05-24 3:12 ` Alexey Kardashevskiy
2014-05-25 10:16 ` Alexander Graf
2014-05-25 13:36 ` David Gibson
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 6/7] vfio: Create VFIOAddressSpace objects as needed Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 7/7] vfio: Add guest side IOMMU support Alexey Kardashevskiy
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=1400821160-25258-2-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).