qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, aliguori@us.ibm.com, stefanha@gmail.com,
	blauwirbel@gmail.com, pbonzini@redhat.com,
	Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v13 3/7] stubs add set_fd_handler and signalfd_available
Date: Fri, 30 Nov 2012 14:17:19 +0800	[thread overview]
Message-ID: <1354256243-8375-4-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)
In-Reply-To: <1354256243-8375-1-git-send-email-xiawenc@linux.vnet.ibm.com>

  These functions are needed by libqblock, so add them into stubs.

Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
---
 stubs/Makefile.objs    |    1 +
 stubs/set-fd-handler.c |    8 ++++++++
 stubs/signalfd.c       |    7 +++++++
 3 files changed, 16 insertions(+), 0 deletions(-)
 create mode 100644 stubs/signalfd.c

diff --git a/stubs/Makefile.objs b/stubs/Makefile.objs
index 035b29a..434a480 100644
--- a/stubs/Makefile.objs
+++ b/stubs/Makefile.objs
@@ -5,4 +5,5 @@ stub-obj-y += fdset-get-fd.o
 stub-obj-y += fdset-remove-fd.o
 stub-obj-y += get-fd.o
 stub-obj-y += set-fd-handler.o
+stub-obj-y += signalfd.o
 stub-obj-$(CONFIG_WIN32) += fd-register.o
diff --git a/stubs/set-fd-handler.c b/stubs/set-fd-handler.c
index 4807b5d..7b4ca4f 100644
--- a/stubs/set-fd-handler.c
+++ b/stubs/set-fd-handler.c
@@ -9,3 +9,11 @@ int qemu_set_fd_handler2(int fd,
 {
     abort();
 }
+
+int qemu_set_fd_handler(int fd,
+                        IOHandler *fd_read,
+                        IOHandler *fd_write,
+                        void *opaque)
+{
+    abort();
+}
diff --git a/stubs/signalfd.c b/stubs/signalfd.c
new file mode 100644
index 0000000..a28d8a2
--- /dev/null
+++ b/stubs/signalfd.c
@@ -0,0 +1,7 @@
+#include "qemu-common.h"
+#include "compatfd.h"
+
+bool qemu_signalfd_available(void)
+{
+    abort();
+}
-- 
1.7.1

  parent reply	other threads:[~2012-11-30  6:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  6:17 [Qemu-devel] [PATCH v13 0/7] libqblock qemu block layer library Wenchao Xia
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 1/7] Build system clean tests directory clearly Wenchao Xia
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 2/7] block export function path_has_protocol Wenchao Xia
2012-11-30  6:17 ` Wenchao Xia [this message]
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 4/7] libqblock build system Wenchao Xia
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 5/7] libqblock API design and type defines Wenchao Xia
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 6/7] libqblock API implement Wenchao Xia
2012-11-30  6:17 ` [Qemu-devel] [PATCH v13 7/7] libqblock test example Wenchao Xia
2012-12-09  4:52 ` [Qemu-devel] [PATCH v13 0/7] libqblock qemu block layer library Wenchao Xia
2012-12-14 10:06 ` Wenchao Xia
2012-12-14 10:17   ` Paolo Bonzini
2013-01-21 11:15     ` 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=1354256243-8375-4-git-send-email-xiawenc@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).