2016-01-27 10:07+0800, Yang Zhang:
> On 2016/1/27 2:22, rkrc...@redhat.com wrote:
>>2016-01-26 09:44+0800, Yang Zhang:
>>>On 2016/1/25 21:59, rkrc...@redhat.com wrote:
>> Also, if wakeup vector were used for wakeup and multicast, we'd be
>> uselessly doing work, because we can't tell
2016-01-27 10:07+0800, Yang Zhang:
> On 2016/1/27 2:22, rkrc...@redhat.com wrote:
>>2016-01-26 09:44+0800, Yang Zhang:
>>>On 2016/1/25 21:59, rkrc...@redhat.com wrote:
>> Also, if wakeup vector were used for wakeup and multicast, we'd be
>> uselessly doing work, because we can't tell
On 2016/1/27 2:22, rkrc...@redhat.com wrote:
2016-01-26 09:44+0800, Yang Zhang:
On 2016/1/25 21:59, rkrc...@redhat.com wrote:
2016-01-25 09:49+0800, Yang Zhang:
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
Not so complicated. We can reuse the wake up
2016-01-26 09:44+0800, Yang Zhang:
> On 2016/1/25 21:59, rkrc...@redhat.com wrote:
>>2016-01-25 09:49+0800, Yang Zhang:
>>>On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
>Not so complicated. We can reuse the wake up vector and check whether the
2016-01-26 09:44+0800, Yang Zhang:
> On 2016/1/25 21:59, rkrc...@redhat.com wrote:
>>2016-01-25 09:49+0800, Yang Zhang:
>>>On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
>Not so complicated. We can reuse the wake up vector and check whether the
On 2016/1/27 2:22, rkrc...@redhat.com wrote:
2016-01-26 09:44+0800, Yang Zhang:
On 2016/1/25 21:59, rkrc...@redhat.com wrote:
2016-01-25 09:49+0800, Yang Zhang:
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
Not so complicated. We can reuse the wake up
On 2016/1/25 21:59, rkrc...@redhat.com wrote:
2016-01-25 09:49+0800, Yang Zhang:
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
Not so complicated. We can reuse the wake up vector and check whether the
interrupt is multicast when one of destination vcpu
> -Original Message-
> From: Radim Krcmár [mailto:rkrc...@redhat.com]
> Sent: Monday, January 25, 2016 10:06 PM
> To: Wu, Feng
> Cc: Paolo Bonzini ; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to remapped mode if the
> interrupt
2016-01-25 12:26+, Wu, Feng:
>> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
>> It may be necessary because IRTE writes (128 bits) are not atomic.
>
> IRTE is updated atomically, I added the patch to support this. Please
> refer to
2016-01-25 09:49+0800, Yang Zhang:
> On 2016/1/22 21:31, rkrc...@redhat.com wrote:
>>2016-01-22 10:03+0800, Yang Zhang:
>>>Not so complicated. We can reuse the wake up vector and check whether the
>>>interrupt is multicast when one of destination vcpu handles it.
>>
>>I'm not sure what you mean
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Monday, January 25, 2016 8:39 PM
> To: Wu, Feng ; Radim Krcmár
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to remapped mode if the
> interrupt is
On 25/01/2016 13:26, Wu, Feng wrote:
>> > It may be necessary because IRTE writes (128 bits) are not atomic.
> IRTE is updated atomically, I added the patch to support this. Please
> refer to 344cb4e0b6f3a0dbef0643eacb4946338eb228c0.
Great, I hadn't noticed that patch. Thanks.
Paolo
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Monday, January 25, 2016 8:23 PM
> To: Radim Krcmár ; Wu, Feng
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to
On 22/01/2016 14:05, Radim Krcmár wrote:
> > This is a good question. I also thought about this before, but after
> > thinking it a bit more, seems we don't need to do this.
> > If we don't do this, the in-flight interrupts will continue to be
> > delivered in PI mode while we are changing it
2016-01-25 12:26+, Wu, Feng:
>> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
>> It may be necessary because IRTE writes (128 bits) are not atomic.
>
> IRTE is updated atomically, I added the patch to support this. Please
> refer to
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Monday, January 25, 2016 8:39 PM
> To: Wu, Feng ; Radim Krcmár
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Monday, January 25, 2016 8:23 PM
> To: Radim Krcmár ; Wu, Feng
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re:
On 25/01/2016 13:26, Wu, Feng wrote:
>> > It may be necessary because IRTE writes (128 bits) are not atomic.
> IRTE is updated atomically, I added the patch to support this. Please
> refer to 344cb4e0b6f3a0dbef0643eacb4946338eb228c0.
Great, I hadn't noticed that patch. Thanks.
Paolo
2016-01-25 09:49+0800, Yang Zhang:
> On 2016/1/22 21:31, rkrc...@redhat.com wrote:
>>2016-01-22 10:03+0800, Yang Zhang:
>>>Not so complicated. We can reuse the wake up vector and check whether the
>>>interrupt is multicast when one of destination vcpu handles it.
>>
>>I'm not sure what you mean
On 2016/1/25 21:59, rkrc...@redhat.com wrote:
2016-01-25 09:49+0800, Yang Zhang:
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
Not so complicated. We can reuse the wake up vector and check whether the
interrupt is multicast when one of destination vcpu
> -Original Message-
> From: Radim Krcmár [mailto:rkrc...@redhat.com]
> Sent: Monday, January 25, 2016 10:06 PM
> To: Wu, Feng
> Cc: Paolo Bonzini ; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover
On 22/01/2016 14:05, Radim Krcmár wrote:
> > This is a good question. I also thought about this before, but after
> > thinking it a bit more, seems we don't need to do this.
> > If we don't do this, the in-flight interrupts will continue to be
> > delivered in PI mode while we are changing it
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
On 2016/1/22 0:35, rkrc...@redhat.com wrote:
2016-01-21 13:44+0800, Yang Zhang:
On 2016/1/21 13:41, Wu, Feng wrote:
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
We may have different understanding on PI
On 2016/1/22 21:31, rkrc...@redhat.com wrote:
2016-01-22 10:03+0800, Yang Zhang:
On 2016/1/22 0:35, rkrc...@redhat.com wrote:
2016-01-21 13:44+0800, Yang Zhang:
On 2016/1/21 13:41, Wu, Feng wrote:
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
We may have different understanding on PI
2016-01-22 10:03+0800, Yang Zhang:
> On 2016/1/22 0:35, rkrc...@redhat.com wrote:
>>2016-01-21 13:44+0800, Yang Zhang:
>>>On 2016/1/21 13:41, Wu, Feng wrote:
>From: Yang Zhang [mailto:yang.zhang...@gmail.com]
>We may have different understanding on PI mode. My understanding is if
>we
2016-01-22 01:49+, Wu, Feng:
>> From: Radim Krčmář [mailto:rkrc...@redhat.com]
>> 2016-01-20 09:42+0800, Feng Wu:
>> > - if (!kvm_intr_is_single_vcpu(kvm, , ))
>> > + if (!kvm_intr_is_single_vcpu(kvm, , )) {
>> > + /*
>> > + * Make sure the
2016-01-22 01:49+, Wu, Feng:
>> From: Radim Krčmář [mailto:rkrc...@redhat.com]
>> 2016-01-20 09:42+0800, Feng Wu:
>> > - if (!kvm_intr_is_single_vcpu(kvm, , ))
>> > + if (!kvm_intr_is_single_vcpu(kvm, , )) {
>> > + /*
>> > + * Make sure the
2016-01-22 10:03+0800, Yang Zhang:
> On 2016/1/22 0:35, rkrc...@redhat.com wrote:
>>2016-01-21 13:44+0800, Yang Zhang:
>>>On 2016/1/21 13:41, Wu, Feng wrote:
>From: Yang Zhang [mailto:yang.zhang...@gmail.com]
>We may have different understanding on PI mode. My understanding is if
>we
On 2016/1/22 0:35, rkrc...@redhat.com wrote:
2016-01-21 13:44+0800, Yang Zhang:
On 2016/1/21 13:41, Wu, Feng wrote:
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
We may have different understanding on PI mode. My understanding is if
we set the IRTE to PI format, than the subsequent
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 12:20 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to remapped mode if the
>
2016-01-21 13:44+0800, Yang Zhang:
> On 2016/1/21 13:41, Wu, Feng wrote:
>>>From: Yang Zhang [mailto:yang.zhang...@gmail.com]
>>>We may have different understanding on PI mode. My understanding is if
>>>we set the IRTE to PI format, than the subsequent interrupt will be
>>>handled in PI mode.
2016-01-20 09:42+0800, Feng Wu:
> When the interrupt is not single destination any more, we need
> to change back IRTE to remapped mode explicitly.
>
> Signed-off-by: Feng Wu
> ---
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> @@ -10764,8 +10764,17 @@ static int
2016-01-21 13:44+0800, Yang Zhang:
> On 2016/1/21 13:41, Wu, Feng wrote:
>>>From: Yang Zhang [mailto:yang.zhang...@gmail.com]
>>>We may have different understanding on PI mode. My understanding is if
>>>we set the IRTE to PI format, than the subsequent interrupt will be
>>>handled in PI mode.
2016-01-20 09:42+0800, Feng Wu:
> When the interrupt is not single destination any more, we need
> to change back IRTE to remapped mode explicitly.
>
> Signed-off-by: Feng Wu
> ---
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> @@ -10764,8 +10764,17 @@ static int
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 12:20 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to remapped
On 2016/1/22 0:35, rkrc...@redhat.com wrote:
2016-01-21 13:44+0800, Yang Zhang:
On 2016/1/21 13:41, Wu, Feng wrote:
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
We may have different understanding on PI mode. My understanding is if
we set the IRTE to PI format, than the subsequent
On 2016/1/21 13:41, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 1:36 PM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject: Re: [PATCH v3 1/4]
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 1:36 PM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to
On 2016/1/21 13:07, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 1:00 PM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject: Re: [PATCH v3 1/4]
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 1:00 PM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to
On 2016/1/21 12:42, Wu, Feng wrote:
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Yang Zhang
Sent: Thursday, January 21, 2016 11:35 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org;
> From: Wu, Feng
> Sent: Thursday, January 21, 2016 12:43 PM
>
> > -Original Message-
> > From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> > Behalf Of Yang Zhang
> > Sent: Thursday, January 21, 2016 11:35 AM
> > To: Wu, Feng ; pbonz...@redhat.com;
> >
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Yang Zhang
> Sent: Thursday, January 21, 2016 11:35 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject:
On 2016/1/21 11:14, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 11:06 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject: Re: [PATCH v3 1/4]
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 11:06 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to
On 2016/1/20 9:42, Feng Wu wrote:
When the interrupt is not single destination any more, we need
to change back IRTE to remapped mode explicitly.
Signed-off-by: Feng Wu
---
arch/x86/kvm/vmx.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx.c
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 11:06 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM:
On 2016/1/21 13:41, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 1:36 PM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject:
> From: Wu, Feng
> Sent: Thursday, January 21, 2016 12:43 PM
>
> > -Original Message-
> > From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> > Behalf Of Yang Zhang
> > Sent: Thursday, January 21, 2016 11:35 AM
> > To: Wu, Feng ; pbonz...@redhat.com;
On 2016/1/21 13:07, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 1:00 PM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject:
On 2016/1/20 9:42, Feng Wu wrote:
When the interrupt is not single destination any more, we need
to change back IRTE to remapped mode explicitly.
Signed-off-by: Feng Wu
---
arch/x86/kvm/vmx.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
On 2016/1/21 12:42, Wu, Feng wrote:
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Yang Zhang
Sent: Thursday, January 21, 2016 11:35 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc:
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Yang Zhang
> Sent: Thursday, January 21, 2016 11:35 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org;
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 1:36 PM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM:
On 2016/1/21 11:14, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Thursday, January 21, 2016 11:06 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
Subject:
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Thursday, January 21, 2016 1:00 PM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: linux-kernel@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM:
56 matches
Mail list logo