From: mrhines@linux.vnet.ibm.com
To: quintela@redhat.com
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, owasserm@redhat.com,
abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com,
pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v6 07/11] rdma: introduce qemu_ram_foreach_block()
Date: Wed, 24 Apr 2013 15:00:52 -0400 [thread overview]
Message-ID: <1366830057-16964-8-git-send-email-mrhines@linux.vnet.ibm.com> (raw)
In-Reply-To: <1366830057-16964-1-git-send-email-mrhines@linux.vnet.ibm.com>
From: "Michael R. Hines" <mrhines@us.ibm.com>
This is used during RDMA initialization in order to
transmit a description of all the RAM blocks to the
peer for later dynamic chunk registration purposes.
Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
---
exec.c | 9 +++++++++
include/exec/cpu-common.h | 5 +++++
2 files changed, 14 insertions(+)
diff --git a/exec.c b/exec.c
index fa1e0c3..0e5a2c3 100644
--- a/exec.c
+++ b/exec.c
@@ -2631,3 +2631,12 @@ bool cpu_physical_memory_is_io(hwaddr phys_addr)
memory_region_is_romd(section->mr));
}
#endif
+
+void qemu_ram_foreach_block(RAMBlockIterFunc func, void *opaque)
+{
+ RAMBlock *block;
+
+ QTAILQ_FOREACH(block, &ram_list.blocks, next) {
+ func(block->host, block->offset, block->length, opaque);
+ }
+}
diff --git a/include/exec/cpu-common.h b/include/exec/cpu-common.h
index 2e5f11f..2900fd6 100644
--- a/include/exec/cpu-common.h
+++ b/include/exec/cpu-common.h
@@ -119,6 +119,11 @@ extern struct MemoryRegion io_mem_rom;
extern struct MemoryRegion io_mem_unassigned;
extern struct MemoryRegion io_mem_notdirty;
+typedef void (RAMBlockIterFunc)(void *host_addr,
+ ram_addr_t offset, ram_addr_t length, void *opaque);
+
+void qemu_ram_foreach_block(RAMBlockIterFunc func, void *opaque);
+
#endif
#endif /* !CPU_COMMON_H */
--
1.7.10.4
next prev parent reply other threads:[~2013-04-24 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 19:00 [Qemu-devel] [PATCH v6 00/11] rdma: migration support mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 01/11] rdma: add documentation mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 02/11] rdma: export yield_until_fd_readable() mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 03/11] rdma: export throughput w/ MigrationStats QMP mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 04/11] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 05/11] rdma: export qemu_fflush() mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 06/11] rdma: introduce ram_handle_compressed() mrhines
2013-04-24 19:00 ` mrhines [this message]
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 08/11] rdma: new QEMUFileOps hooks mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 09/11] rdma: introduce capability x-rdma-pin-all mrhines
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 10/11] rdma: core logic mrhines
2013-04-25 19:45 ` Anthony Liguori
2013-04-25 19:49 ` Michael R. Hines
2013-04-25 20:13 ` Anthony Liguori
2013-04-24 19:00 ` [Qemu-devel] [PATCH v6 11/11] rdma: send pc.ram mrhines
2013-04-24 21:50 ` [Qemu-devel] [PATCH v6 00/11] rdma: migration support Paolo Bonzini
2013-04-24 23:48 ` Michael R. Hines
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=1366830057-16964-8-git-send-email-mrhines@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=gokul@us.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).