From: mrhines@linux.vnet.ibm.com
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, quintela@redhat.com, knoel@redhat.com,
owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com,
gokul@us.ibm.com, pbonzini@redhat.com, chegu_vinod@hp.com
Subject: [Qemu-devel] [PATCH v12 08/15] rdma: introduce qemu_ram_foreach_block()
Date: Tue, 25 Jun 2013 21:35:34 -0400 [thread overview]
Message-ID: <1372210541-28092-9-git-send-email-mrhines@linux.vnet.ibm.com> (raw)
In-Reply-To: <1372210541-28092-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.
Reviewed-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Chegu Vinod <chegu_vinod@hp.com>
Tested-by: Chegu Vinod <chegu_vinod@hp.com>
Tested-by: Michael R. Hines <mrhines@us.ibm.com>
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 0b0118b..2e6fc00 100644
--- a/exec.c
+++ b/exec.c
@@ -2630,3 +2630,12 @@ bool cpu_physical_memory_is_io(hwaddr phys_addr)
memory_region_is_romd(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 e061e21..92a4223 100644
--- a/include/exec/cpu-common.h
+++ b/include/exec/cpu-common.h
@@ -113,6 +113,11 @@ void cpu_physical_memory_write_rom(hwaddr addr,
extern struct MemoryRegion io_mem_rom;
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-06-26 1:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 1:35 [Qemu-devel] [PATCH v12 00/15] rdma: migration support mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 01/15] rdma: add documentation mrhines
2013-06-26 1:48 ` [Qemu-devel] [PATCH v12 00/15] rdma: migration support Michael R. Hines
2013-06-27 22:41 ` [Qemu-devel] [PATCH v12 01/15] rdma: add documentation Eric Blake
2013-06-27 22:48 ` Michael R. Hines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 02/15] rdma: introduce qemu_update_position() mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 03/15] rdma: export yield_until_fd_readable() mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 04/15] rdma: export throughput w/ MigrationStats QMP mrhines
2013-06-27 23:02 ` Eric Blake
2013-06-28 13:13 ` Michael R. Hines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 05/15] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 06/15] rdma: export qemu_fflush() mrhines
2013-06-26 1:35 ` mrhines [this message]
2013-06-27 19:24 ` [Qemu-devel] [PATCH v12 08/15] rdma: introduce qemu_ram_foreach_block() Peter Maydell
2013-06-27 19:56 ` Michael R. Hines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 09/15] rdma: new QEMUFileOps hooks mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 10/15] rdma: introduce capability x-rdma-pin-all mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 11/15] rdma: core logic mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 12/15] rdma: send pc.ram mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 13/15] rdma: allow state transitions between other states besides ACTIVE mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 14/15] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition mrhines
2013-06-26 1:35 ` [Qemu-devel] [PATCH v12 15/15] rdma: account for the time spent in MIG_STATE_SETUP through QMP mrhines
2013-06-27 22:58 ` Eric Blake
2013-06-28 7:15 ` Paolo Bonzini
2013-06-28 13:15 ` Michael R. Hines
2013-06-28 13:32 ` Eric Blake
2013-06-28 14:45 ` Michael R. Hines
2013-06-28 13:14 ` 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=1372210541-28092-9-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=chegu_vinod@hp.com \
--cc=gokul@us.ibm.com \
--cc=knoel@redhat.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).