All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [KVM PATCH v9 2/2] KVM: add iosignalfd support
Date: Tue, 07 Jul 2009 09:30:38 -0400	[thread overview]
Message-ID: <4A534DFE.8000205@novell.com> (raw)
In-Reply-To: <20090707132136.GB7578@redhat.com>

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

Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2009 at 08:56:43AM -0400, Gregory Haskins wrote:
>   
>> Michael S. Tsirkin wrote:
>>     
>>> On Tue, Jul 07, 2009 at 03:27:49PM +0300, Avi Kivity wrote:
>>>   
>>>       
>>>> On 07/07/2009 03:22 PM, Michael S. Tsirkin wrote:
>>>>     
>>>>         
>>>>> On Tue, Jul 07, 2009 at 02:53:18PM +0300, Avi Kivity wrote:
>>>>>    
>>>>>       
>>>>>           
>>>>>>>> +		/* address-range must be precise for a hit */
>>>>>>>>
>>>>>>>>          
>>>>>>>>             
>>>>>>>>                 
>>>>>>> So there's apparently no way to specify that
>>>>>>> you want 1,2, or 4 byte writes at address X?
>>>>>>>
>>>>>>>        
>>>>>>>           
>>>>>>>               
>>>>>> Why would you want that?
>>>>>>      
>>>>>>         
>>>>>>             
>>>>> Donnu. Why would anyone want to catch 8 byte writes at all?
>>>>>    
>>>>>       
>>>>>           
>>>> One of the natural write sizes.
>>>>
>>>>     
>>>>         
>>>>> Seriously, why add artificial limitations?
>>>>> IMO, addr=0,len=1 and addr=0,len=2 should not conflict.
>>>>>
>>>>>    
>>>>>       
>>>>>           
>>>> They should not conflict, but a two byte write need not hit a one byte  
>>>> registration.
>>>>     
>>>>         
>>> Yes. That's exactly what I'm saying. I think it should be possible to
>>> create 2 fds:
>>>
>>> addr = 0
>>> len = 1
>>> addr = 0
>>> len = 2
>>> and at most one will ever trigger.
>>>
>>> But current code will not let you create the second one.
>>>
>>>   
>>>       
>> Note that this was by design to keep the code simple since we don't have
>> a (known) use case for overlap.  At the very least, you have to address
>> how data subsets are handled.  But do we really need that functionality?
>>
>> -Greg
>>
>>     
>
> Hey, forget about overlap. Overlap does not exist as a concept.  You now
> spend a lot of effort to detect it. Kill all that code, and just do
> this on assignment:
>
> list_for_each(...)
> 	if (rhs->add == lhs->addr && rhs->len == lhs->len &&
> 	    (rhs->wildcard || lhs->wildcard || rhs->data == lhs->data))
> 		return -EEXIST;
>
>   
I like it.  Will do for v10.

Thanks Michael,
-Greg


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

  reply	other threads:[~2009-07-07 13:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 20:33 [KVM PATCH v9 0/2] iosignalfd Gregory Haskins
2009-07-06 20:33 ` [KVM PATCH v9 1/2] KVM: make io_bus interface more robust Gregory Haskins
2009-07-07 11:20   ` Michael S. Tsirkin
2009-07-07 17:26     ` Gregory Haskins
2009-07-08  7:47       ` Michael S. Tsirkin
2009-07-08 11:40         ` Gregory Haskins
2009-07-06 20:33 ` [KVM PATCH v9 2/2] KVM: add iosignalfd support Gregory Haskins
2009-07-07 11:20   ` Michael S. Tsirkin
2009-07-07 11:53     ` Avi Kivity
2009-07-07 12:22       ` Michael S. Tsirkin
2009-07-07 12:27         ` Avi Kivity
2009-07-07 12:51           ` Michael S. Tsirkin
2009-07-07 12:56             ` Gregory Haskins
2009-07-07 13:21               ` Michael S. Tsirkin
2009-07-07 13:30                 ` Gregory Haskins [this message]
2009-07-07 12:56             ` Avi Kivity
2009-07-07 13:17       ` Gregory Haskins
2009-07-07 12:15     ` Gregory Haskins
2009-07-07 12:48       ` Michael S. Tsirkin
2009-07-07 12:56         ` Avi Kivity
2009-07-07 12:58           ` Michael S. Tsirkin
2009-07-07 13:16         ` Gregory Haskins
2009-07-07  9:22 ` [KVM PATCH v9 0/2] iosignalfd 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=4A534DFE.8000205@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=mst@redhat.com \
    /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.