On December 20, 2016 1:37 PM, Tian, Kevin wrote:
>> From: Xuquan (Quan Xu) [mailto:xuqu...@huawei.com]
>> Sent: Friday, December 16, 2016 5:40 PM
>I suppose you've verified this new version, but still would like get your
>explicit confirmation - did you still see time accuracy issue in your side?
>Have you tried other guest OS types other than Win7-32?
>
Kevin, I have tested it again..
__without__ my patch, for win7-64, the wall clock time looks working fine..
It seems the issue is only for win-32..
There is a easy way to reproduce:
*pCPU should be v3 ..(my pCPU is """Intel(R) Xeon(R) CPU E5-2620 v3 @
2.40GHz""")
* more than 2 vCPUs for win32 guest.
Than run the following .bat in win32 guest:
:abcd
echo 11111
goto :abcd
Could Intel test team help me verify it?
>> ---
>> xen/arch/x86/hvm/vmx/intr.c | 15 ++++++++++++---
>> 1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/xen/arch/x86/hvm/vmx/intr.c b/xen/arch/x86/hvm/vmx/intr.c
>> index 639a705..d7a5716 100644
>> --- a/xen/arch/x86/hvm/vmx/intr.c
>> +++ b/xen/arch/x86/hvm/vmx/intr.c
>> - if (pt_vector != -1)
>> - vmx_set_eoi_exit_bitmap(v, pt_vector);
>> + if ( pt_vector != -1 ) {
>> + if ( intack.vector > pt_vector )
>> + vmx_set_eoi_exit_bitmap(v, intack.vector);
>> + else
>> + vmx_set_eoi_exit_bitmap(v, pt_vector);
>> + }
>
>Above can be simplified as one line change:
> if ( pt_vector != -1 )
> vmx_set_eoi_exit_bitmap(v, intack.vector);
>
I have verified this change.. it is working..
Could I send out v4 with this changes?
Quan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
