* Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
@ 2009-03-30 2:22 Xu, Jiajun
2009-03-30 7:07 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Xu, Jiajun @ 2009-03-30 2:22 UTC (permalink / raw)
To: 'kvm@vger.kernel.org'
Hi All,
This is our Weekly KVM Testing Report against lastest kvm.git
0c77713470debc666a07dc40080d728272bb58b9 and kvm-userspace.git
1223a029b36b0d9e73af76bcc274bb770f814886.
One New Issue:
================================================
1. perfctr wrmsr warning when booting 64bit RHEl5.3
https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
Five Old Issues:
================================================
1. 32bits Rhel5/FC6 guest may fail to reboot after installation
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1991647&group_id=180599
2. failure to migrate guests with more than 4GB of RAM
https://sourceforge.net/tracker/index.php?func=detail&aid=1971512&group_id=180599&atid=893831
3. OpenSuse10.2 can not be installed
http://sourceforge.net/tracker/index.php?func=detail&aid=2088475&group_id=180599&atid=893831
4. Fail to Save Restore Guest
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2175042&group_id=180599
5. hotplug inexistent device will kill guest
https://sourceforge.net/tracker/index.php?func=detail&aid=2432316&group_id=180599&atid=893831
Test environment
================================================
Platform A
Stoakley/Clovertown
CPU 4
Memory size 8G'
Report Summary on IA32-pae
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel 8 5 3 0 0
gtest 16 16 0 0 0
=====================================================================
control_panel 8 5 3 0 0
:KVM_256M_guest_PAE_gPAE 1 1 0 0 0
:KVM_linux_win_PAE_gPAE 1 1 0 0 0
:KVM_two_winxp_PAE_gPAE 1 1 0 0 0
:KVM_four_sguest_PAE_gPA 1 0 1 0 0
:KVM_1500M_guest_PAE_gPA 1 1 0 0 0
:KVM_LM_Continuity_PAE_g 1 0 1 0 0
:KVM_LM_SMP_PAE_gPAE 1 1 0 0 0
:KVM_SR_Continuity_PAE_g 1 0 1 0 0
gtest 16 16 0 0 0
:ltp_nightly_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:reboot_xp_PAE_gPAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 1 1 0 0 0
:boot_up_acpi_win2k3_PAE 1 1 0 0 0
:boot_smp_acpi_win2k3_PA 1 1 0 0 0
:boot_smp_acpi_win2k_PAE 1 1 0 0 0
:boot_up_win2008_PAE_gPA 1 1 0 0 0
:boot_up_acpi_win2k_PAE_ 1 1 0 0 0
:boot_smp_acpi_xp_PAE_gP 1 1 0 0 0
:boot_up_noacpi_win2k_PA 1 1 0 0 0
:boot_smp_vista_PAE_gPAE 1 1 0 0 0
:boot_smp_win2008_PAE_gP 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
=====================================================================
Total 24 21 3 0 0
Report Summary on IA32e
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel 17 9 8 0 0
gtest 23 23 0 0 0
=====================================================================
control_panel 17 9 8 0 0
:KVM_4G_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_linux_win_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_gPAE 1 0 1 0 0
:KVM_SR_Continuity_64_gP 1 0 1 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
:KVM_four_dguest_64_gPAE 1 1 0 0 0
:KVM_SR_SMP_64_gPAE 1 0 1 0 0
:KVM_LM_Continuity_64_g3 1 0 1 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_Continuity_64_gP 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 0 1 0 0
:KVM_SR_Continuity_64_g3 1 0 1 0 0
:KVM_two_winxp_64_gPAE 1 1 0 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_256M_guest_64_g32e 1 0 1 0 0
gtest 23 23 0 0 0
:boot_up_acpi_64_gPAE 1 1 0 0 0
:boot_up_noacpi_xp_64_gP 1 1 0 0 0
:boot_base_kernel_64_gPA 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
:kb_nightly_64_gPAE 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_up_noacpi_win2k_64 1 1 0 0 0
:boot_smp_acpi_xp_64_gPA 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
:boot_smp_vista_64_gPAE 1 1 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_up_win2008_64_gPAE 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_vista_64_gPAE 1 1 0 0 0
:ltp_nightly_64_gPAE 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_up_noacpi_win2k3_6 1 1 0 0 0
=====================================================================
Total 40 32 8 0 0
Test environment
================================================
Platform B
Nehalem
CPU 8
Memory size 4G'
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 8 4 4 0 0
control_panel_ept 4 2 2 0 0
control_panel 4 0 4 0 0
control_panel_vpid 4 2 2 0 0
gtest_vpid 4 4 0 0 0
gtest_ept 2 2 0 0 0
gtest 4 4 0 0 0
gtest_ept_vpid 14 12 2 0 0
=====================================================================
control_panel_ept_vpid 8 4 4 0 0
:KVM_256M_guest_PAE_gPAE 1 0 1 0 0
:KVM_linux_win_PAE_gPAE 1 1 0 0 0
:KVM_two_winxp_PAE_gPAE 1 1 0 0 0
:KVM_four_sguest_PAE_gPA 1 1 0 0 0
:KVM_1500M_guest_PAE_gPA 1 1 0 0 0
:KVM_LM_SMP_PAE_gPAE 1 0 1 0 0
:KVM_LM_Continuity_PAE_g 1 0 1 0 0
:KVM_SR_Continuity_PAE_g 1 0 1 0 0
control_panel_ept 4 2 2 0 0
:KVM_four_sguest_PAE_gPA 1 1 0 0 0
:KVM_1500M_guest_PAE_gPA 1 1 0 0 0
:KVM_linux_win_PAE_gPAE 1 0 1 0 0
:KVM_SR_Continuity_PAE_g 1 0 1 0 0
control_panel 4 0 4 0 0
:KVM_four_sguest_PAE_gPA 1 0 1 0 0
:KVM_1500M_guest_PAE_gPA 1 0 1 0 0
:KVM_linux_win_PAE_gPAE 1 0 1 0 0
:KVM_LM_SMP_PAE_gPAE 1 0 1 0 0
control_panel_vpid 4 2 2 0 0
:KVM_four_sguest_PAE_gPA 1 0 1 0 0
:KVM_1500M_guest_PAE_gPA 1 1 0 0 0
:KVM_linux_win_PAE_gPAE 1 1 0 0 0
:KVM_LM_SMP_PAE_gPAE 1 0 1 0 0
gtest_vpid 4 4 0 0 0
:boot_smp_vista_PAE_gPAE 1 1 0 0 0
:reboot_xp_PAE_gPAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 1 1 0 0 0
:boot_up_win2008_PAE_gPA 1 1 0 0 0
gtest_ept 2 2 0 0 0
:boot_smp_acpi_win2k3_PA 1 1 0 0 0
:boot_smp_acpi_win2k_PAE 1 1 0 0 0
gtest 4 4 0 0 0
:boot_smp_win2008_PAE_gP 1 1 0 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_smp_acpi_xp_PAE_gP 1 1 0 0 0
:boot_up_noacpi_win2k_PA 1 1 0 0 0
gtest_ept_vpid 14 12 2 0 0
:boot_up_acpi_PAE_gPAE 1 0 1 0 0
:ltp_nightly_PAE_gPAE 1 0 1 0 0
:boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 1 1 0 0 0
:boot_up_acpi_win2k3_PAE 1 1 0 0 0
:boot_smp_acpi_win2k3_PA 1 1 0 0 0
:boot_up_win2008_PAE_gPA 1 1 0 0 0
:boot_up_acpi_win2k_PAE_ 1 1 0 0 0
:boot_smp_acpi_win2k_PAE 1 1 0 0 0
:boot_smp_acpi_xp_PAE_gP 1 1 0 0 0
:boot_up_noacpi_win2k_PA 1 1 0 0 0
:boot_smp_win2008_PAE_gP 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
=====================================================================
Total 44 30 14 0 0
Report Summary on IA32e
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 16 7 7 2 0
control_panel_ept 5 2 3 0 0
control_panel 5 3 2 0 0
control_panel_vpid 7 4 3 0 0
gtest_vpid 4 4 0 0 0
gtest_ept 1 1 0 0 0
gtest 6 6 0 0 0
vtd 5 2 3 0 0
vtd_ept_vpid 5 2 3 0 0
gtest_ept_vpid 20 18 2 0 0
=====================================================================
control_panel_ept_vpid 16 7 7 2 0
:KVM_SR_SMP_64_gPAE 1 0 1 0 0
:KVM_LM_Continuity_64_g3 1 0 0 1 0
:KVM_four_sguest_64_gPAE 1 1 0 0 0
:KVM_linux_win_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_Continuity_64_gP 1 0 0 1 0
:KVM_SR_Continuity_64_gP 1 0 1 0 0
:KVM_LM_SMP_64_gPAE 1 0 1 0 0
:KVM_1500M_guest_64_g32e 1 0 1 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_two_winxp_64_gPAE 1 1 0 0 0
:KVM_SR_Continuity_64_g3 1 0 1 0 0
:KVM_256M_guest_64_g32e 1 0 1 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
:KVM_four_dguest_64_gPAE 1 1 0 0 0
control_panel_ept 5 2 3 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 0 1 0 0
:KVM_four_sguest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_1500M_guest_64_gPAE 1 0 1 0 0
control_panel 5 3 2 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_linux_win_64_gPAE 1 1 0 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_1500M_guest_64_gPAE 1 0 1 0 0
control_panel_vpid 7 4 3 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_SR_SMP_64_gPAE 1 0 1 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_gPAE 1 1 0 0 0
:KVM_two_winxp_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_1500M_guest_64_gPAE 1 0 1 0 0
gtest_vpid 4 4 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_vista_64_gPAE 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
gtest_ept 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
gtest 6 6 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:boot_smp_acpi_xp_64_gPA 1 1 0 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
:boot_up_win2008_64_gPAE 1 1 0 0 0
:boot_smp_vista_64_g32e 1 1 0 0 0
vtd 5 2 3 0 0
:one_pcie_scp_64_g32e 1 1 0 0 0
:one_pcie_up_xp_64_g32e 1 1 0 0 0
:one_pcie_up_64_g32e 1 1 0 0 0
:one_pcie_smp_xp_64_g32e 1 1 0 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
vtd_ept_vpid 5 2 0 0 0
:one_pcie_scp_64_g32e 1 1 0 0 0
:one_pcie_up_xp_64_g32e 1 1 0 0 0
:one_pcie_up_64_g32e 1 1 0 0 0
:one_pcie_smp_xp_64_g32e 1 1 0 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
gtest_ept_vpid 20 18 2 0 0
:boot_up_acpi_64_gPAE 1 0 1 0 0
:boot_up_noacpi_xp_64_gP 1 1 0 0 0
:boot_base_kernel_64_gPA 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
:kb_nightly_64_gPAE 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_up_noacpi_win2k_64 1 1 0 0 0
:boot_smp_acpi_xp_64_gPA 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
:boot_up_acpi_64_g32e 1 0 1 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_up_win2008_64_gPAE 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:ltp_nightly_64_gPAE 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_up_noacpi_win2k3_6 1 1 0 0 0
=====================================================================
Total 74 55 17 2 0
Best Regards,
Jiajun
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 2:22 Biweekly KVM Test report, kernel 0c7771... userspace 1223a0 Xu, Jiajun
@ 2009-03-30 7:07 ` Avi Kivity
2009-03-30 11:17 ` Amit Shah
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2009-03-30 7:07 UTC (permalink / raw)
To: Xu, Jiajun, Amit Shah; +Cc: 'kvm@vger.kernel.org'
Xu, Jiajun wrote:
> Hi All,
>
> This is our Weekly KVM Testing Report against lastest kvm.git
> 0c77713470debc666a07dc40080d728272bb58b9 and kvm-userspace.git
> 1223a029b36b0d9e73af76bcc274bb770f814886.
>
> One New Issue:
> ================================================
> 1. perfctr wrmsr warning when booting 64bit RHEl5.3
> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>
This is the architectural performance counting msr which was enabled in
4f76231 (KVM: x86: Ignore reads to EVNTSEL MSRs). Amit, can you check
if appropriate cpuid leaf 10 reporting will fix this?
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 7:07 ` Avi Kivity
@ 2009-03-30 11:17 ` Amit Shah
2009-03-30 13:55 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Amit Shah @ 2009-03-30 11:17 UTC (permalink / raw)
To: Avi Kivity; +Cc: Xu, Jiajun, 'kvm@vger.kernel.org'
On (Mon) Mar 30 2009 [10:07:58], Avi Kivity wrote:
>> 1. perfctr wrmsr warning when booting 64bit RHEl5.3
>> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>
> This is the architectural performance counting msr which was enabled in
> 4f76231 (KVM: x86: Ignore reads to EVNTSEL MSRs). Amit, can you check
> if appropriate cpuid leaf 10 reporting will fix this?
We already report 0s for the cpuid leaf 10; we need to report 0x3f in
EBX for leaf 10 to denote events corresponding to the bits aren't
available.
I checked and it didn't help (we can't rely on guests to abide by cpuid
flags)
Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 11:17 ` Amit Shah
@ 2009-03-30 13:55 ` Avi Kivity
2009-03-30 14:48 ` Amit Shah
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2009-03-30 13:55 UTC (permalink / raw)
To: Amit Shah; +Cc: Xu, Jiajun, 'kvm@vger.kernel.org'
Amit Shah wrote:
> On (Mon) Mar 30 2009 [10:07:58], Avi Kivity wrote:
>
>
>>> 1. perfctr wrmsr warning when booting 64bit RHEl5.3
>>> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>>>
>> This is the architectural performance counting msr which was enabled in
>> 4f76231 (KVM: x86: Ignore reads to EVNTSEL MSRs). Amit, can you check
>> if appropriate cpuid leaf 10 reporting will fix this?
>>
>
> We already report 0s for the cpuid leaf 10; we need to report 0x3f in
> EBX for leaf 10 to denote events corresponding to the bits aren't
> available.
>
> I checked and it didn't help (we can't rely on guests to abide by cpuid
> flags)
>
I see this in the code:
> /*
> * Check whether the Architectural PerfMon supports
> * Unhalted Core Cycles Event or not.
> * NOTE: Corresponding bit = 0 in ebx indicates event present.
> */
> cpuid(10, &(eax.full), &ebx, &unused, &unused);
> if ((eax.split.mask_length <
> (ARCH_PERFMON_UNHALTED_CORE_CYCLES_INDEX+1)) ||
> (ebx & ARCH_PERFMON_UNHALTED_CORE_CYCLES_PRESENT))
> return 0;
>
So I think it can be done.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 13:55 ` Avi Kivity
@ 2009-03-30 14:48 ` Amit Shah
2009-03-30 15:02 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Amit Shah @ 2009-03-30 14:48 UTC (permalink / raw)
To: Avi Kivity; +Cc: Xu, Jiajun, 'kvm@vger.kernel.org'
On (Mon) Mar 30 2009 [16:55:05], Avi Kivity wrote:
> Amit Shah wrote:
>> On (Mon) Mar 30 2009 [10:07:58], Avi Kivity wrote:
>>
>>
>>>> 1. perfctr wrmsr warning when booting 64bit RHEl5.3
>>>> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>>>>
>>> This is the architectural performance counting msr which was enabled
>>> in 4f76231 (KVM: x86: Ignore reads to EVNTSEL MSRs). Amit, can you
>>> check if appropriate cpuid leaf 10 reporting will fix this?
>>>
>>
>> We already report 0s for the cpuid leaf 10; we need to report 0x3f in
>> EBX for leaf 10 to denote events corresponding to the bits aren't
>> available.
>>
>> I checked and it didn't help (we can't rely on guests to abide by cpuid
>> flags)
>>
>
> I see this in the code:
>
>> /*
>> * Check whether the Architectural PerfMon supports
>> * Unhalted Core Cycles Event or not.
>> * NOTE: Corresponding bit = 0 in ebx indicates event present.
>> */
>> cpuid(10, &(eax.full), &ebx, &unused, &unused);
>> if ((eax.split.mask_length <
>> (ARCH_PERFMON_UNHALTED_CORE_CYCLES_INDEX+1)) ||
>> (ebx & ARCH_PERFMON_UNHALTED_CORE_CYCLES_PRESENT))
>> return 0;
>>
>
> So I think it can be done.
Only if the guest kernel (or module accessing those registers) look at
the cpuid output, right? I checked this for the Kaspersky AV on Windows,
the crash bug I was solving and that program doesn't seem to check
cpuid.
RHEL 5.3 is based on 2.6.18 and this patch appears to have entered in
2.6.21. I saw this on 5.3 as well.
Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 14:48 ` Amit Shah
@ 2009-03-30 15:02 ` Avi Kivity
2009-03-31 8:56 ` Amit Shah
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2009-03-30 15:02 UTC (permalink / raw)
To: Amit Shah; +Cc: Xu, Jiajun, 'kvm@vger.kernel.org'
Amit Shah wrote:
>>
>>> /*
>>> * Check whether the Architectural PerfMon supports
>>> * Unhalted Core Cycles Event or not.
>>> * NOTE: Corresponding bit = 0 in ebx indicates event present.
>>> */
>>> cpuid(10, &(eax.full), &ebx, &unused, &unused);
>>> if ((eax.split.mask_length <
>>> (ARCH_PERFMON_UNHALTED_CORE_CYCLES_INDEX+1)) ||
>>> (ebx & ARCH_PERFMON_UNHALTED_CORE_CYCLES_PRESENT))
>>> return 0;
>>>
>>>
>> So I think it can be done.
>>
>
> Only if the guest kernel (or module accessing those registers) look at
> the cpuid output, right? I checked this for the Kaspersky AV on Windows,
> the crash bug I was solving and that program doesn't seem to check
> cpuid.
>
The only way to solve all possible cases is to implement the performance
counters MSRs. That's not going to happen in a hurry, we're looking at
making the known cases work.
> RHEL 5.3 is based on 2.6.18 and this patch appears to have entered in
> 2.6.21. I saw this on 5.3 as well.
>
The snippet I quoted came from RHEL 5.3. It checks cpuid so we should
be able to make it fail gracefully.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
2009-03-30 15:02 ` Avi Kivity
@ 2009-03-31 8:56 ` Amit Shah
0 siblings, 0 replies; 7+ messages in thread
From: Amit Shah @ 2009-03-31 8:56 UTC (permalink / raw)
To: Avi Kivity; +Cc: Xu, Jiajun, 'kvm@vger.kernel.org'
On (Mon) Mar 30 2009 [18:02:16], Avi Kivity wrote:
> Amit Shah wrote:
>>>
>>>> /*
>>>> * Check whether the Architectural PerfMon supports
>>>> * Unhalted Core Cycles Event or not.
>>>> * NOTE: Corresponding bit = 0 in ebx indicates event present.
>>>> */
>>>> cpuid(10, &(eax.full), &ebx, &unused, &unused);
>>>> if ((eax.split.mask_length <
>>>> (ARCH_PERFMON_UNHALTED_CORE_CYCLES_INDEX+1)) ||
>>>> (ebx & ARCH_PERFMON_UNHALTED_CORE_CYCLES_PRESENT))
>>>> return 0;
>>>>
>>>>
>>> So I think it can be done.
>>>
>>
>> Only if the guest kernel (or module accessing those registers) look at
>> the cpuid output, right? I checked this for the Kaspersky AV on Windows,
>> the crash bug I was solving and that program doesn't seem to check
>> cpuid.
>>
>
> The only way to solve all possible cases is to implement the performance
> counters MSRs. That's not going to happen in a hurry, we're looking at
> making the known cases work.
Looks like it does get solved...
>> RHEL 5.3 is based on 2.6.18 and this patch appears to have entered in
>> 2.6.21. I saw this on 5.3 as well.
>>
>
> The snippet I quoted came from RHEL 5.3. It checks cpuid so we should
> be able to make it fail gracefully.
Our default CPU is qemu64, which has cpuid till level 2. Trying with
-cpu core2duo, this doesn't happen (even without setting EBX to the 0x3f
value) on both, RHEL 5.3 and Win+Kaspersky guests.
qemu64 loosely models some AMD CPU type. I guess we can update it to
expose cpuid levels upto 10 (and leave xlevel to the current value).
That should take care of this.
Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-03-31 8:56 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-03-30 2:22 Biweekly KVM Test report, kernel 0c7771... userspace 1223a0 Xu, Jiajun
2009-03-30 7:07 ` Avi Kivity
2009-03-30 11:17 ` Amit Shah
2009-03-30 13:55 ` Avi Kivity
2009-03-30 14:48 ` Amit Shah
2009-03-30 15:02 ` Avi Kivity
2009-03-31 8:56 ` Amit Shah
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).