From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH 05/11] memory: add ref/unref
Date: Tue, 25 Jun 2013 13:13:21 +0200 [thread overview]
Message-ID: <1372158807-19715-6-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1372158807-19715-1-git-send-email-pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
include/exec/memory.h | 30 ++++++++++++++++++++++++++++++
memory.c | 14 ++++++++++++++
2 files changed, 44 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 763297e..c842d48 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -270,6 +270,36 @@ void memory_region_init(MemoryRegion *mr,
struct Object *owner,
const char *name,
uint64_t size);
+
+/**
+ * memory_region_ref: Add 1 to a memory region's reference count
+ *
+ * Whenever memory regions are accessed outside the BQL, they need to be
+ * preserved against hot-unplug. MemoryRegions actually do not have their
+ * own reference count; they piggyback on a QOM object, their "owner".
+ * This function adds a reference to the owner.
+ *
+ * All MemoryRegions must have an owner if they can disappear, even if the
+ * device they belong to operates exclusively under the BQL. This is because
+ * the region could be returned at any time by memory_region_find, and this
+ * is usually under guest control.
+ *
+ * @mr: the #MemoryRegion
+ */
+void memory_region_ref(MemoryRegion *mr);
+
+/**
+ * memory_region_unref: Remove 1 to a memory region's reference count
+ *
+ * Whenever memory regions are accessed outside the BQL, they need to be
+ * preserved against hot-unplug. MemoryRegions actually do not have their
+ * own reference count; they piggyback on a QOM object, their "owner".
+ * This function removes a reference to the owner and possibly destroys it.
+ *
+ * @mr: the #MemoryRegion
+ */
+void memory_region_unref(MemoryRegion *mr);
+
/**
* memory_region_init_io: Initialize an I/O memory region.
*
diff --git a/memory.c b/memory.c
index 61b3f25..b74078c 100644
--- a/memory.c
+++ b/memory.c
@@ -1105,6 +1105,20 @@ Object *memory_region_owner(MemoryRegion *mr)
return mr->owner;
}
+void memory_region_ref(MemoryRegion *mr)
+{
+ if (mr && mr->owner) {
+ object_ref(mr->owner);
+ }
+}
+
+void memory_region_unref(MemoryRegion *mr)
+{
+ if (mr && mr->owner) {
+ object_unref(mr->owner);
+ }
+}
+
uint64_t memory_region_size(MemoryRegion *mr)
{
if (int128_eq(mr->size, int128_2_64())) {
--
1.8.1.4
next prev parent reply other threads:[~2013-06-25 11:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 11:13 [Qemu-devel] [PATCH 00/11] Memory patches, part 4: region ownership Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 01/11] memory: add owner argument to initialization functions Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 02/11] memory: destroy phys_sections one by one Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 03/11] exec: simplify destruction of the phys map Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 04/11] memory: add getter for owner Paolo Bonzini
2013-06-25 11:13 ` Paolo Bonzini [this message]
2013-06-25 11:13 ` [Qemu-devel] [PATCH 06/11] memory: add ref/unref calls Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 07/11] exec: add a reference to the region returned by address_space_translate Paolo Bonzini
2013-06-28 13:41 ` Jan Kiszka
2013-06-28 15:23 ` Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 08/11] exec: check MRU in qemu_ram_addr_from_host Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 09/11] exec: move qemu_ram_addr_from_host_nofail to cputlb.c Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 10/11] memory: return MemoryRegion from qemu_ram_addr_from_host Paolo Bonzini
2013-06-25 11:13 ` [Qemu-devel] [PATCH 11/11] memory: ref/unref memory across address_space_map/unmap Paolo Bonzini
2013-06-28 13:46 ` [Qemu-devel] [PATCH 00/11] Memory patches, part 4: region ownership Jan Kiszka
2013-06-28 15:12 ` 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=1372158807-19715-6-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).