[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49FFA1AB.5000307@novell.com>
Date: Mon, 04 May 2009 22:17:15 -0400
From: Gregory Haskins <ghaskins@...ell.com>
To: Al Viro <viro@...IV.linux.org.uk>
CC: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, avi@...hat.com,
davidel@...ilserver.org
Subject: Re: [KVM PATCH v4 1/2] eventfd: export eventfd interfaces for module
use
Al Viro wrote:
> On Mon, May 04, 2009 at 01:57:45PM -0400, Gregory Haskins wrote:
>
>> @@ -56,6 +57,7 @@ int eventfd_signal(struct file *file, int n)
>>
>> return n;
>> }
>> +EXPORT_SYMBOL_GPL(eventfd_signal);
>>
>
> perhaps, but...
>
>
>> @@ -197,6 +199,7 @@ struct file *eventfd_fget(int fd)
>>
>> return file;
>> }
>> +EXPORT_SYMBOL_GPL(eventfd_fget);
>>
>
> this one looks very odd. Could you show legitimate users?
>
Hi Al,
I plan on using this in a similar way as the AIO io_submit function does
today for the next version of the virtual-bus patches. That is,
userspace allocates an eventfd (in this case, via kvm_irqfd() and the
kernel side code you have been reviewing) and subsequently submits the
fd to a unique virtual-bus instance in the kernel via an ioctl(). This
will ultimately associate the vbus instance dynamically with the kvm
instance in a loosely coupled relationship. Vbus may be compiled as a
module, thus the export.
-Greg
Download attachment "signature.asc" of type "application/pgp-signature" (267 bytes)
Powered by blists - more mailing lists