From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH] kvm: pass value to in_range callback Date: Thu, 25 Jun 2009 22:23:29 +0300 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 Cc: Gregory Haskins , avi@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mtosatti@redhat.com, paulmck@linux.vnet.ibm.com, markmc@redhat.com To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57825 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752580AbZFYTYB (ORCPT ); Thu, 25 Jun 2009 15:24:01 -0400 Content-Disposition: inline In-Reply-To: <4A438E8F.4080008@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 > > --- > > > > 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?