On 2012-04-17 14:06, Avi Kivity wrote: > On 04/17/2012 03:03 PM, Gleb Natapov wrote: >>> >>> KVM_MAX_VCPUS. >>> >> Ah, so you are worried about malicious guest configuring pit to >> broadcast to all its vcpus. > > Yes - it can introduce huge amounts of latency this way which is exactly > what Jan is trying to prevent. > > Though I'm not sure spin_lock_irq() in the realtime tree actually > disables irqs (but it's certainly not a good idea in mainline; it's > nasty even with just the spinlock). This depends on how you declare the spin lock type - raw or normal. The former will disable irqs, the latter not even preemption (but become a mutex). Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- 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
