>>> On Tue, Apr 24, 2007 at 5:17 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>
>> Are there any other userspace sleeps that we need to handle (e.g. maybe
> AIO)? If so, one way to handle this is to mark the exportable state of the
> VCPU
Gregory Haskins wrote:
On Sun, Apr 22, 2007 at 4:50 AM, in message <[EMAIL PROTECTED]>,
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Gregory Haskins wrote:
>>
>>> /*
>>> +* Signal that we have transitioned back to host mode
>>> +*/
>>> + spin_lock_irqsave
>>> On Sun, Apr 22, 2007 at 4:50 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>> /*
>> + * Signal that we have transitioned back to host mode
>> + */
>> +spin_lock_irqsave(&vcpu- >irq.lock, irq_flags);
>> +vcpu- >irq.gues
Gregory Haskins wrote:
> The VCPU executes synchronously w.r.t. userspace today, and therefore
> interrupt injection is pretty straight forward. However, we will soon need
> to be able to inject interrupts asynchronous to the execution of the VCPU
> due to the introduction of SMP, paravirtualized
The VCPU executes synchronously w.r.t. userspace today, and therefore
interrupt injection is pretty straight forward. However, we will soon need
to be able to inject interrupts asynchronous to the execution of the VCPU
due to the introduction of SMP, paravirtualized drivers, and asynchronous
hype
