From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 06/14] stubs: Add stubs for ram block API
Date: Thu, 25 Jan 2018 13:46:40 +0800 [thread overview]
Message-ID: <20180125054648.18747-7-famz@redhat.com> (raw)
In-Reply-To: <20180125054648.18747-1-famz@redhat.com>
These functions will be wanted by block-obj-y but the actual definition
is in obj-y, so stub them to keep the linker happy.
Signed-off-by: Fam Zheng <famz@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20180110091846.10699-2-famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20180116060901.17413-2-famz@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
---
stubs/Makefile.objs | 1 +
stubs/ram-block.c | 16 ++++++++++++++++
2 files changed, 17 insertions(+)
create mode 100644 stubs/ram-block.c
diff --git a/stubs/Makefile.objs b/stubs/Makefile.objs
index 8cfe34328a..2d59d84091 100644
--- a/stubs/Makefile.objs
+++ b/stubs/Makefile.objs
@@ -42,3 +42,4 @@ stub-obj-y += vmgenid.o
stub-obj-y += xen-common.o
stub-obj-y += xen-hvm.o
stub-obj-y += pci-host-piix.o
+stub-obj-y += ram-block.o
diff --git a/stubs/ram-block.c b/stubs/ram-block.c
new file mode 100644
index 0000000000..cfa5d8678f
--- /dev/null
+++ b/stubs/ram-block.c
@@ -0,0 +1,16 @@
+#include "qemu/osdep.h"
+#include "exec/ramlist.h"
+#include "exec/cpu-common.h"
+
+void ram_block_notifier_add(RAMBlockNotifier *n)
+{
+}
+
+void ram_block_notifier_remove(RAMBlockNotifier *n)
+{
+}
+
+int qemu_ram_foreach_block(RAMBlockIterFunc func, void *opaque)
+{
+ return 0;
+}
--
2.14.3
next prev parent reply other threads:[~2018-01-25 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 5:46 [Qemu-devel] [PULL 00/14] Block and docker patches Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 01/14] docker: change Fedora base image to fedora:27 Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 02/14] lockable: add QemuLockable Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 03/14] coroutine-lock: convert CoQueue to use QemuLockable Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 04/14] coroutine-lock: make qemu_co_enter_next thread-safe Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 05/14] curl: convert to CoQueue Fam Zheng
2018-01-25 5:46 ` Fam Zheng [this message]
2018-01-25 5:46 ` [Qemu-devel] [PULL 07/14] util: Introduce vfio helpers Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 08/14] block: Add VFIO based NVMe driver Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 09/14] block: Introduce buf register API Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 10/14] block/nvme: Implement .bdrv_(un)register_buf Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 11/14] qemu-img: Map bench buffer Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 12/14] block: Move NVMe constants to a separate header Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 13/14] docs: Add section for NVMe VFIO driver Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 14/14] qapi: Add NVMe driver options to the schema Fam Zheng
2018-01-25 13:51 ` [Qemu-devel] [PULL 00/14] Block and docker patches Peter Maydell
2018-01-25 14:16 ` Fam Zheng
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=20180125054648.18747-7-famz@redhat.com \
--to=famz@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).