Gregory Haskins wrote:
On Wed, May 16, 2007 at 6:05 AM, in message <[EMAIL PROTECTED]>,
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Gregory Haskins wrote:
>>
>>>
>>>
Later we'll have vcpu and thread_info point to each other and then you
can do that
>>> On Wed, May 16, 2007 at 6:05 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>>
>>> Later we'll have vcpu and thread_info point to each other and then you
>>> can do that kind of optimization.
>>>
>>
>> I am not familiar with thread_i
Gregory Haskins wrote:
>
>> Later we'll have vcpu and thread_info point to each other and then you
>> can do that kind of optimization.
>>
>
> I am not familiar with thread_info, but if it solves the dangling pointer
> problem, that sounds great.
It's fairly tricky, but it's the right way
>>> On Tue, May 15, 2007 at 3:28 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>
>>
>> I like having both states tracked, because it allows me to optimize the vcpu
> interrupt if the context of the injection is the same as the execution. E.g.
Gregory Haskins wrote:
On Mon, May 14, 2007 at 11:45 AM, in message <[EMAIL PROTECTED]>,
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Gregory Haskins wrote:
>>
> index 059f074..0f6cc32 100644
> --- a/drivers/kvm/kvm.h
> +++ b/drivers/kvm/kvm.h
> @@ - 3
>>> On Mon, May 14, 2007 at 11:45 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
index 059f074..0f6cc32 100644
--- a/drivers/kvm/kvm.h
+++ b/drivers/kvm/kvm.h
@@ - 329,6 +329,8 @@ struct kvm_vcpu_irq {
struct kvm_ir
Gregory Haskins wrote:
>>> index 059f074..0f6cc32 100644
>>> --- a/drivers/kvm/kvm.h
>>> +++ b/drivers/kvm/kvm.h
>>> @@ - 329,6 +329,8 @@ struct kvm_vcpu_irq {
>>> struct kvm_irqdevice dev;
>>> int pending;
>>> int deferred;
>>> + struct task_struct
>>> On Mon, May 14, 2007 at 5:34 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> 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
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
hyper
10 matches
Mail list logo
