Date: Thu, 25 Jun 2009 22:23:29 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gregory Haskins <gregory.haskins@gmail.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
Message-ID: <20090625192329.GB3239@redhat.com>
References: <20090625125333.GB7166@redhat.com> <4A438E8F.4080008@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A438E8F.4080008@gmail.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1086
Lines: 31

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/