On 02/07/2011 06:59 PM, Jan Kiszka wrote:
>
> (well, actually, cpufreq_notifier and kvm_arch_hardware_enable are
> already non preemptible, and the stats code should just go away?)
The stats code is trivial to convert, so it doesn't matter.
Removal is easier.
But what about mmu_shrink and its list_move_tail? How is this
synchronized against kvm_destroy_vm - already today?
kvm_destroy_vm() takes kvm_lock. If a vm is destroyed before
mmu_shrink(), mmu_shrink() will never see it. If we reach mmu_shrink()
before kvm_destroy_vm(), the latter will wait until mmu_shrink() is done.
--
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
