On 04/24/2012 07:21 PM, Christian Borntraeger wrote: > On 24/04/12 18:15, Avi Kivity wrote: > >>> instead of looking like you're doing the processing for every vcpu. The > >>> loop is just a slow lookup which might some day be replaced by a table > >>> lookup. > >> > >> Ok. We might also have a kvm_vcpu_on_spin_directed in common code, > >> Would you prefer that? > > > > You mean a function that takes a vcpu and tries to yield_to() it? Or > > something else? > > Or a cpu id (number). But yes, something like that. > > I dont know if that will be of use for x86 (e.g. parvirtual > ticketlocks or something like that). > > It looks like kvm_vcpu_on_spin() can use it. -- error compiling committee.c: too many arguments to function -- 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
