From: Gregory Haskins <ghaskins@novell.com>
To: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, avi@redhat.com, --cc=mtosatti@redhat.com
Subject: [KVM PATCH v3 1/4] eventfd: export eventfd interfaces for module use
Date: Thu, 21 May 2009 12:49:31 -0400 [thread overview]
Message-ID: <20090521164931.14617.27675.stgit@dev.haskins.net> (raw)
In-Reply-To: <20090521164241.14617.92951.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-21 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 16:49 [KVM PATCH v3 0/4] iosignalfd Gregory Haskins
2009-05-21 16:49 ` Gregory Haskins [this message]
2009-05-21 16:49 ` [KVM PATCH v3 2/4] kvm: add return value to kvm_io_bus_register_dev Gregory Haskins
2009-05-21 16:51 [KVM PATCH v3 0/4] iosignalfd Gregory Haskins
2009-05-21 16:51 ` [KVM PATCH v3 1/4] eventfd: export eventfd interfaces for module use Gregory Haskins
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=20090521164931.14617.27675.stgit@dev.haskins.net \
--to=ghaskins@novell.com \
--cc=--cc=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).