From: Gregory Haskins <ghaskins@novell.com>
To: kvm@vger.kernel.org
Cc: viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org,
avi@redhat.com, davidel@xmailserver.org
Subject: [KVM PATCH v7 1/3] eventfd: export eventfd interfaces for module use
Date: Tue, 12 May 2009 14:26:50 -0400 [thread overview]
Message-ID: <20090512182650.26131.21334.stgit@dev.haskins.net> (raw)
In-Reply-To: <20090512181134.26131.10023.stgit@dev.haskins.net>
We want to use eventfd from KVM which can be compiled as a module, so
export the interfaces.
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
---
fs/eventfd.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
index 2a701d5..3f0e197 100644
--- a/fs/eventfd.c
+++ b/fs/eventfd.c
@@ -16,6 +16,7 @@
#include <linux/anon_inodes.h>
#include <linux/eventfd.h>
#include <linux/syscalls.h>
+#include <linux/module.h>
struct eventfd_ctx {
wait_queue_head_t wqh;
@@ -56,6 +57,7 @@ int eventfd_signal(struct file *file, int n)
return n;
}
+EXPORT_SYMBOL_GPL(eventfd_signal);
static int eventfd_release(struct inode *inode, struct file *file)
{
@@ -197,6 +199,7 @@ struct file *eventfd_fget(int fd)
return file;
}
+EXPORT_SYMBOL_GPL(eventfd_fget);
SYSCALL_DEFINE2(eventfd2, unsigned int, count, int, flags)
{
next prev parent reply other threads:[~2009-05-12 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 18:26 [KVM PATCH v7 0/3] kvm: eventfd interfaces (formerly irqfd) Gregory Haskins
2009-05-12 18:26 ` Gregory Haskins [this message]
2009-05-12 19:02 ` [KVM PATCH v7 1/3] eventfd: export eventfd interfaces for module use Davide Libenzi
2009-05-12 18:26 ` [KVM PATCH v7 2/3] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-05-14 9:47 ` Avi Kivity
2009-05-14 11:52 ` Gregory Haskins
2009-05-14 12:20 ` Avi Kivity
2009-05-14 13:12 ` Gregory Haskins
2009-05-14 11:22 ` Avi Kivity
2009-05-14 15:52 ` Gregory Haskins
2009-05-15 3:22 ` Davide Libenzi
2009-05-15 3:35 ` Gregory Haskins
2009-05-12 18:27 ` [KVM PATCH v7 3/3] kvm: add iofd support Gregory Haskins
2009-05-12 19:05 ` Gregory Haskins
2009-05-12 19:29 ` [KVM PATCH v7.1] " Gregory Haskins
2009-05-12 22:17 ` [KVM PATCH v7.2] " Gregory Haskins
2009-05-13 2:46 ` Gregory Haskins
2009-05-14 11:11 ` [KVM PATCH v7 3/3] " Avi Kivity
2009-05-14 12:02 ` Gregory Haskins
2009-05-14 12:22 ` Avi Kivity
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=20090512182650.26131.21334.stgit@dev.haskins.net \
--to=ghaskins@novell.com \
--cc=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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