* Rik van Riel (riel@xxxxxxxxxx) wrote: > On 12/02/2010 08:18 PM, Chris Wright wrote: > >* Rik van Riel (riel@xxxxxxxxxx) wrote: > >>Keep track of which task is running a KVM vcpu. This helps us > >>figure out later what task to wake up if we want to boost a > >>vcpu that got preempted. > >> > >>Unfortunately there are no guarantees that the same task > >>always keeps the same vcpu, so we can only track the task > >>across a single "run" of the vcpu. > > > >So shouldn't it confine to KVM_RUN? The other vcpu_load callers aren't > >always a vcpu in a useful runnable state. > > Yeah, probably. If you want I can move the setting of > vcpu->task to kvm_vcpu_ioctl. Or maybe setting in sched_out and unsetting in sched_in. -- 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
