Re: [PATCH] kvm: pass value to in_range callback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx>
> >>> ---
> >>>
> >>> 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.

-- 
MST
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux