public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
	avi@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com,
	paulmck@linux.vnet.ibm.com, markmc@redhat.com
Subject: Re: [PATCH] kvm: pass value to in_range callback
Date: Thu, 25 Jun 2009 15:33:15 -0400	[thread overview]
Message-ID: <4A43D0FB.2040005@gmail.com> (raw)
In-Reply-To: <20090625193016.GC3239@redhat.com>

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

Michael S. Tsirkin wrote:
> On Thu, Jun 25, 2009 at 03:25:12PM -0400, Gregory Haskins wrote:
>   
>> Michael S. Tsirkin wrote:
>>     
>>> On Thu, Jun 25, 2009 at 10:49:51AM -0400, Gregory Haskins wrote:
>>>   
>>>       
>>>> Michael S. Tsirkin wrote:
>>>>     
>>>>         
>>>>> For write transactions, pass the value written to in_range checks so
>>>>> that we can make each iosignalfd a separate device on kvm bus.
>>>>>
>>>>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>>>>> ---
>>>>>
>>>>> Reposting with a subject now. Sorry.
>>>>>
>>>>> Avi, can you please merge this patch in kvm.git so that
>>>>> Gregory can use it for iosignalfd? Once bus has RCU
>>>>> we'll be able to remove in_range completely, but
>>>>> let's do it step by step.
>>>>>   
>>>>>       
>>>>>           
>>>> I think this patch will just make more churn for me, not less.  You have
>>>> now convinced me that your io_range-less approach is better.  ;)
>>>>
>>>> Lets just fix the RCU thing and do it right.  Patch is under development
>>>> as we speak.
>>>>
>>>> -Greg
>>>>     
>>>>         
>>> So - let's go ahead with this one?
>>>
>>>   
>>>       
>> Whatever you think is best and/or gets us to the end goal the fastest ;)
>>
>> -Greg
>>
>>     
>
> It's weekend here. If you can look at rcu meanwhile, go ahead.
> Or I will next week.
>
>   
I started looking into it, but it gets kind of messy and is really
conducive to getting rid of in-range at the same time.  So it probably
makes sense to wait until that effort is fully underway.  I'll let you
tackle it and we can sync up later next week.

Thanks, and have a great weekend.
-Greg


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

      reply	other threads:[~2009-06-25 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 12:53 [PATCH] kvm: pass value to in_range callback Michael S. Tsirkin
2009-06-25 14:49 ` Gregory Haskins
2009-06-25 19:23   ` Michael S. Tsirkin
2009-06-25 19:25     ` Gregory Haskins
2009-06-25 19:30       ` Michael S. Tsirkin
2009-06-25 19:33         ` Gregory Haskins [this message]

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=4A43D0FB.2040005@gmail.com \
    --to=gregory.haskins@gmail.com \
    --cc=avi@redhat.com \
    --cc=ghaskins@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox