On 09/27/2009 03:46 PM, Joerg Roedel wrote:
We can't find exactly which vcpu, but we can:
- rule out threads that are not vcpus for this guest
- rule out threads that are already running
A major problem with sleep() is that it effectively reduces the vm
priority relative to guests that don't have spinlock contention. By
selecting a random nonrunnable vcpu belonging to this guest, we at least
preserve the guest's timeslice.
Ok, that makes sense. But before trying that we should probably try to
call just yield() instead of schedule()? I remember someone from our
team here at AMD did this for Xen a while ago and already had pretty
good results with that. Xen has a completly other scheduler but maybe
its worth trying?
yield() is a no-op in CFS.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
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
