Re: [PATCH 4/6] Handle vcpu init/sipi by calling a function on vcpu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/15/2009 01:11 PM, Gleb Natapov wrote:
On Mon, Jun 15, 2009 at 01:03:39PM +0300, Avi Kivity wrote:
On 06/14/2009 01:52 PM, Gleb Natapov wrote:
Instead of having special case in vcpu event loop.


I'm a little worried about two vcpus INITing each other simultaneously
and deadlocking.  INIT/SIPI are async events, the initiator should not
wait for them.

I thought to add on_vcpu_async() for that (if this case is worth warring about).

A generic on_vcpu_async() would need to allocate, that might be expoitable.

--
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux