kvm-ow...@vger.kernel.org wrote on 07/06/2012 15:19:14:
> >> The guest can still mask interrupts above that limit via cli, no? > >> So the only measures that save us from CPU hogging guests are the > >> preemption timer and kicking via NMI. Or what am I missing? > > > > Nothing :) As we described in the paper, this is what we do to avoid > > this situation. > > So the other measures are redundant, right? They only seem to complicate > the approach without any gain, that is my point. We described in the paper all the mechanisms we thought could be used. Which mechanisms are sufficient/preferable/simpler ? I think we are back to the KVM<->Linux dependencies and whenever we are talking about hypervisors in general or a specific implementation for KVM. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
