From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Keith Busch <keith.busch@intel.com>,
qemu-block@nongnu.org, Fam Zheng <famz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Eric Blake <eblake@redhat.com>,
alex.williamson@redhat.com, Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Karl Rister <krister@redhat.com>
Subject: [Qemu-devel] [PATCH v6 1/9] stubs: Add stubs for ram block API
Date: Tue, 16 Jan 2018 14:08:53 +0800 [thread overview]
Message-ID: <20180116060901.17413-2-famz@redhat.com> (raw)
In-Reply-To: <20180116060901.17413-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>
---
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-16 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 6:08 [Qemu-devel] [PATCH v6 0/9] block: Add VFIO based driver for NVMe device Fam Zheng
2018-01-16 6:08 ` Fam Zheng [this message]
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 2/9] util: Introduce vfio helpers Fam Zheng
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 3/9] block: Add VFIO based NVMe driver Fam Zheng
2018-02-13 19:18 ` Eric Blake
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 4/9] block: Introduce buf register API Fam Zheng
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 5/9] block/nvme: Implement .bdrv_(un)register_buf Fam Zheng
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 6/9] qemu-img: Map bench buffer Fam Zheng
2018-01-16 6:08 ` [Qemu-devel] [PATCH v6 7/9] block: Move NVMe constants to a separate header Fam Zheng
2018-01-16 6:09 ` [Qemu-devel] [PATCH v6 8/9] docs: Add section for NVMe VFIO driver Fam Zheng
2018-01-16 6:09 ` [Qemu-devel] [PATCH v6 9/9] qapi: Add NVMe driver options to the schema Fam Zheng
2018-01-22 12:26 ` [Qemu-devel] [PATCH v6 0/9] block: Add VFIO based driver for NVMe device Stefan Hajnoczi
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=20180116060901.17413-2-famz@redhat.com \
--to=famz@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=keith.busch@intel.com \
--cc=krister@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).