From: Gregory Haskins <ghaskins@novell.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, viro@ZenIV.linux.org.uk,
linux-kernel@vger.kernel.org, davidel@xmailserver.org
Subject: Re: [KVM PATCH v7 3/3] kvm: add iofd support
Date: Thu, 14 May 2009 08:02:23 -0400 [thread overview]
Message-ID: <4A0C084F.3040706@novell.com> (raw)
In-Reply-To: <4A0BFC56.9090601@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]
Avi Kivity wrote:
> Gregory Haskins wrote:
>> iofd is a mechanism to register PIO/MMIO regions to trigger an eventfd
>> signal when written to. Userspace can register any arbitrary address
>> with a corresponding eventfd.
>>
>>
>
> Please start a separate patchset for this so I can merge irqfd.
Ack. Will spin a new split series with your irqfd review changes
>
>>
>> diff --git a/include/linux/kvm.h b/include/linux/kvm.h
>> index dfc4bcc..99b6e45 100644
>> --- a/include/linux/kvm.h
>> +++ b/include/linux/kvm.h
>> @@ -292,6 +292,17 @@ struct kvm_guest_debug {
>> struct kvm_guest_debug_arch arch;
>> };
>>
>> +#define KVM_IOFD_FLAG_DEASSIGN (1 << 0)
>> +#define KVM_IOFD_FLAG_PIO (1 << 1)
>> +
>> +struct kvm_iofd {
>> + __u64 addr;
>> + __u32 len;
>> + __u32 fd;
>> + __u32 flags;
>> + __u8 pad[12];
>> +};
>> +
>>
> Please add a data match capability. virtio uses a write with the data
> containing the queue ID, and we want a separate event for each queue.
How about "u64 cookie" ?
>
>
>> * kvm trace categories
>> @@ -508,6 +519,7 @@ struct kvm_irqfd {
>> #define KVM_DEASSIGN_DEV_IRQ _IOW(KVMIO, 0x75, struct
>> kvm_assigned_irq)
>> #define KVM_ASSIGN_IRQFD _IOW(KVMIO, 0x76, struct kvm_irqfd)
>> #define KVM_DEASSIGN_IRQFD _IOW(KVMIO, 0x77, __u32)
>> +#define KVM_IOFD _IOW(KVMIO, 0x78, struct kvm_iofd)
>>
>
> Too general a name. It's not doing IO, just sending out notifications.
Hmm...good point. I was trying to reflect "[MM/P]IO-FD". How about
"IOSIGNALFD"
>
> Why have assign/deassign for irqfd and a single ioctl for iofd?
Heh.. irqfd "liked" two because the deassign only needed a u32. iofd
needed more or less the same structure for both so I guess I thought I
would be "slick" and condense the vectors. Will fix so they are
symmetrical.
>
> The rest looks good.
>
I will also submit a patch to fix the io_bus stuff so that registrations
can gracefully fail instead of BUG_ON(), and to provide an unregister
function.
Thanks Avi,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-05-14 12:02 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 ` [KVM PATCH v7 1/3] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-12 19:02 ` 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 [this message]
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=4A0C084F.3040706@novell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.