Liuqiming (John) wrote on 2015-10-10:
>
> On 2015/10/10 14:32, Zhang, Yang Z wrote:
>> Zhang, Yang Z wrote on 2015-09-24:
>>> Liuqiming (John) wrote on 2015-09-24:
On 2015/9/24 11:25, Zhang, Yang Z wrote:
it completed, the following vmentry will pick up the pending interrupt.
On 2015/10/10 14:32, Zhang, Yang Z wrote:
Zhang, Yang Z wrote on 2015-09-24:
Liuqiming (John) wrote on 2015-09-24:
On 2015/9/24 11:25, Zhang, Yang Z wrote:
it completed, the following vmentry will pick up the pending interrupt.
If you send the ipi unconditionally, actually it is received by
On 2015/9/24 11:25, Zhang, Yang Z wrote:
Liuqiming (John) wrote on 2015-09-24:
On 2015/9/23 21:41, Zhang, Yang Z wrote:
Hanweidong (Randy) wrote on 2015-09-23:
Zhang, Yang Z wrote on ent: 2015年9月23日 11:51:
VCPU_KICK_SOFTIRQ when post interrupt to vm.
Zhang, Yang Z wrote on 2015-09-08:
Liuqiming (John) wrote on 2015-09-24:
>
>
> On 2015/9/24 11:25, Zhang, Yang Z wrote:
>> Liuqiming (John) wrote on 2015-09-24:
>>> On 2015/9/23 21:41, Zhang, Yang Z wrote:
Hanweidong (Randy) wrote on 2015-09-23:
> Zhang, Yang Z wrote on ent: 2015年9月23日 11:51:
>> VCPU_KICK_SOFTIRQ
On Wed, Sep 23, 2015 at 10:18 AM, Zhang, Yang Z wrote:
> George Dunlap wrote on 2015-09-23:
>> On Wed, Sep 23, 2015 at 8:42 AM, Jan Beulich wrote:
>> On 23.09.15 at 05:50, wrote:
--- a/xen/arch/x86/hvm/vmx/vmx.c
Jan Beulich wrote on 2015-09-23:
On 23.09.15 at 11:15, wrote:
>> Jan Beulich wrote on 2015-09-23:
>> On 23.09.15 at 05:50, wrote:
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -1678,8 +1678,9 @@ static
> -Original Message-
> From: Zhang, Yang Z [mailto:yang.z.zh...@intel.com]
> Sent: 2015年9月23日 11:51
> To: Liuqiming (John); Hanweidong (Randy); Jan Beulich
> Cc: Zhangwei (FF); xen-de...@lists.xenproject.org
> Subject: RE: [Xen-devel] [PATCH] Remove a set operation for
>
Hanweidong (Randy) wrote on 2015-09-23:
>
>
> Zhang, Yang Z wrote on ent: 2015年9月23日 11:51:
>> VCPU_KICK_SOFTIRQ when post interrupt to vm.
>>
>> Zhang, Yang Z wrote on 2015-09-08:
>>> Liuqiming (John) wrote on 2015-09-08:
Ok, I will try to explain, correct me if I got anything wrong:
>>> On 23.09.15 at 05:50, wrote:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -1678,8 +1678,9 @@ static void __vmx_deliver_posted_interrupt(struct vcpu
> *v)
> {
> unsigned int cpu = v->processor;
>
> -if (
On Wed, Sep 23, 2015 at 8:42 AM, Jan Beulich wrote:
On 23.09.15 at 05:50, wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -1678,8 +1678,9 @@ static void __vmx_deliver_posted_interrupt(struct vcpu
>> *v)
>>
Jan Beulich wrote on 2015-09-23:
On 23.09.15 at 05:50, wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -1678,8 +1678,9 @@ static void __vmx_deliver_posted_interrupt(struct
> vcpu *v)
>> {
>> unsigned int cpu =
George Dunlap wrote on 2015-09-23:
> On Wed, Sep 23, 2015 at 8:42 AM, Jan Beulich wrote:
> On 23.09.15 at 05:50, wrote:
>>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>>> @@ -1678,8 +1678,9 @@ static void
>
>>> On 23.09.15 at 11:08, wrote:
> On Wed, Sep 23, 2015 at 8:42 AM, Jan Beulich wrote:
> On 23.09.15 at 05:50, wrote:
>>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>>> @@ -1678,8 +1678,9 @@
>>> On 23.09.15 at 11:15, wrote:
> Jan Beulich wrote on 2015-09-23:
> On 23.09.15 at 05:50, wrote:
>>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>>> @@ -1678,8 +1678,9 @@ static void
On 2015/9/23 21:41, Zhang, Yang Z wrote:
Hanweidong (Randy) wrote on 2015-09-23:
Zhang, Yang Z wrote on ent: 2015年9月23日 11:51:
VCPU_KICK_SOFTIRQ when post interrupt to vm.
Zhang, Yang Z wrote on 2015-09-08:
Liuqiming (John) wrote on 2015-09-08:
Ok, I will try to explain, correct me if I
Liuqiming (John) wrote on 2015-09-24:
> On 2015/9/23 21:41, Zhang, Yang Z wrote:
>> Hanweidong (Randy) wrote on 2015-09-23:
>>>
>>> Zhang, Yang Z wrote on ent: 2015年9月23日 11:51:
VCPU_KICK_SOFTIRQ when post interrupt to vm.
Zhang, Yang Z wrote on 2015-09-08:
> Liuqiming (John)
Zhang, Yang Z wrote on 2015-09-08:
> Liuqiming (John) wrote on 2015-09-08:
>> Ok, I will try to explain, correct me if I got anything wrong:
>>
>> The problem here is not interrupts lost but interrupts not delivered
>> in time.
>>
>> there are basically two path to inject an interrupt into VM
On 18/09/15 12:40, Zhang, Yang Z wrote:
> Jan Beulich wrote on 2015-09-18:
> "Zhang, Yang Z" 09/18/15 2:29 AM >>>
>>> Zhang, Yang Z wrote on 2015-09-08:
>>> I have a quick check on current code. I am curious that is current Xen
>>> preemptive?
>>>
>>> Also, when return
Jan Beulich wrote on 2015-09-18:
"Zhang, Yang Z" 09/18/15 2:29 AM >>>
>> Zhang, Yang Z wrote on 2015-09-08:
>> I have a quick check on current code. I am curious that is current Xen
>> preemptive?
>>
>> Also, when return from an interrupt handler, hypervisor didn't
Andrew Cooper wrote on 2015-09-18:
> On 18/09/15 12:40, Zhang, Yang Z wrote:
>> Jan Beulich wrote on 2015-09-18:
>> "Zhang, Yang Z" 09/18/15 2:29 AM >>>
Zhang, Yang Z wrote on 2015-09-08:
I have a quick check on current code. I am curious that is current
On Fri, 2015-09-18 at 11:50 +, Zhang, Yang Z wrote:
> Andrew Cooper wrote on 2015-09-18:
> > On 18/09/15 12:40, Zhang, Yang Z wrote:
> > > But it only happens before do vmentry. Is it possible that
> > VCPU been preempted at any time when running in hypervisor mode?
> >
> > All vcpus may be
Zhang, Yang Z wrote on 2015-09-08:
> Liuqiming (John) wrote on 2015-09-08:
>> Ok, I will try to explain, correct me if I got anything wrong:
>>
>> The problem here is not interrupts lost but interrupts not delivered
>> in time.
>>
>> there are basically two path to inject an interrupt into VM
>>> "Zhang, Yang Z" 09/18/15 2:29 AM >>>
>Zhang, Yang Z wrote on 2015-09-08:
>I have a quick check on current code. I am curious that is current Xen
> preemptive?
> Also, when return from an interrupt handler, hypervisor didn't check
> whether reschedule is needed if the
Liuqiming (John) wrote on 2015-09-08:
> Ok, I will try to explain, correct me if I got anything wrong:
>
> The problem here is not interrupts lost but interrupts not delivered in
> time.
>
> there are basically two path to inject an interrupt into VM (or vCPU to
> another vCPU):
> Path 1, the
>>> On 08.09.15 at 10:10, wrote:
> Liuqiming (John) wrote on 2015-09-08:
>> Ok, I will try to explain, correct me if I got anything wrong:
>>
>> The problem here is not interrupts lost but interrupts not delivered in
>> time.
>>
>> there are basically two path to inject
I believe this also has something to do with a windows guest boot hang
issue.
It randomly occured, when boot a guest has windows 2008 os and pv-driver
installed.
The boot process hangs when wait xenstored replay event signal.
It can be reproduced after hundreds reboot using the xen staging
>>> On 07.09.15 at 16:24, wrote:
> I believe this also has something to do with a windows guest boot hang
> issue.
>
> It randomly occured, when boot a guest has windows 2008 os and pv-driver
> installed.
> The boot process hangs when wait xenstored replay event
Hanweidong (Randy) wrote on 2015-09-08:
>
> Jan Beulich wrote on ent: 2015年9月7日 22:46:
>> Subject: Re: [Xen-devel] [PATCH] Remove a set operation for
>> VCPU_KICK_SOFTIRQ when post interrupt to vm.
>>
> On 07.09.15 at 16:24, wrote:
>>> I believe this also has
Ok, I will try to explain, correct me if I got anything wrong:
The problem here is not interrupts lost but interrupts not delivered in
time.
there are basically two path to inject an interrupt into VM (or vCPU to
another vCPU):
Path 1, the traditional way:
1) set bit in vlapic IRR
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 2015年9月7日 22:46
> To: Liuqiming (John)
> Cc: Hanweidong (Randy); Zhangwei (FF); yang.z.zh...@intel.com; xen-
> de...@lists.xenproject.org
> Subject: Re: [Xen-devel] [PATCH] Remove a set operation for
>
30 matches
Mail list logo