public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [KVM PATCH v2 4/4] kvm: add iosignalfd support
Date: Sun, 17 May 2009 22:37:09 -0400	[thread overview]
Message-ID: <4A10C9D5.7000408@novell.com> (raw)
In-Reply-To: <4A10704E.1080301@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

Avi Kivity wrote:
> Gregory Haskins wrote:
>> +
>> +struct _iosignalfd {
>>   
>
> Why the underscore?  It's unorthodox for a structure.

I tend to do that to denote "this is a private structure", but it makes
more sense if we are building a factory interface for a corresponding
public version of the structure of the same name.  In this case, I do
not think I was using that pattern, but old habits die hard. ;)  I will
get rid of this extra underscore in the next rev.

>
>
>> +    u64                  cookie;
>> +    u64                  addr;
>> +    size_t               length;
>> +    struct file         *file;
>> +    struct list_head     list;
>> +    struct kvm_io_device dev;
>> +};
>>   
>
> How will that work with multiple identical addresses and different
> cookies?  Will the code iterate over all of them and just fire for one?
Yeah, primarily because I think the io_bus code will stop once it finds
the first in_range() match.  But I put this logic in anyway in
preparation for the future when we may perhaps support such a notion
(similar to what you had me do with the irqfd side).

-Greg



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]

  reply	other threads:[~2009-05-18  2:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 16:28 [KVM PATCH v2 0/4] iosignalfd Gregory Haskins
2009-05-15 16:28 ` [KVM PATCH v2 1/4] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-15 16:28 ` [KVM PATCH v2 2/4] kvm: add return value to kvm_io_bus_register_dev Gregory Haskins
2009-05-17 20:10   ` Avi Kivity
2009-05-18  2:31     ` Gregory Haskins
2009-05-15 16:28 ` [KVM PATCH v2 3/4] kvm: add io_bus unregister function Gregory Haskins
2009-05-15 16:28 ` [KVM PATCH v2 4/4] kvm: add iosignalfd support Gregory Haskins
2009-05-17 20:15   ` Avi Kivity
2009-05-18  2:37     ` Gregory Haskins [this message]
2009-05-15 16:35 ` [KVM PATCH v2 0/4] iosignalfd 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=4A10C9D5.7000408@novell.com \
    --to=ghaskins@novell.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