Re: WARNING: at vsmp_64.c: is_vsmp_box()
Hi Fengguang, On Thu, Aug 23, 2012 at 08:55:15AM +0800, Fengguang Wu wrote: > Hi Ido, > > The below warning should be introduced by this commit at tip/master: > > commit c00679af441c5be76e195deed2c76fef65a5d102 > Author: Ido Yariv > CommitDate: Wed Aug 22 10:48:05 2012 +0200 > > x86/vsmp: Use hypervisor layer for initialization > > [0.00] tsc: Detected 3200.098 MHz processor > [0.00] [ cut here ] > [0.00] WARNING: at > /c/kernel-tests/src/tip/arch/x86/kernel/vsmp_64.c:158 is_vsmp_box+0xa1/0xb0() > [0.00] Hardware name: Bochs > [0.00] Pid: 0, comm: swapper/0 Not tainted 3.6.0-rc2-01612-g595b3f3 > #292 > [0.00] Call Trace: > [0.00] [] ? warn_slowpath_common+0x7a/0xb0 > [0.00] [] ? is_vsmp_box+0xa1/0xb0 > [0.00] [] ? apic_is_clustered_box+0x34/0x4c > [0.00] [] ? unsynchronized_tsc+0x23/0x71 > [0.00] [] ? tsc_init+0xc2/0xed > [0.00] [] ? start_kernel+0x3fd/0x47a > [0.00] [] ? repair_env_string+0x5b/0x5b > [0.00] [] ? x86_64_start_kernel+0x105/0x114 If another hypervisor is detected, vsmp's detect callback will not be called, triggering this warning. This commit is is no longer in tip for other reasons, but this issue will be addressed in the next revision of this patch. Thanks, Ido. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: WARNING: at vsmp_64.c: is_vsmp_box()
Hi Fengguang, On Thu, Aug 23, 2012 at 08:55:15AM +0800, Fengguang Wu wrote: Hi Ido, The below warning should be introduced by this commit at tip/master: commit c00679af441c5be76e195deed2c76fef65a5d102 Author: Ido Yariv i...@wizery.com CommitDate: Wed Aug 22 10:48:05 2012 +0200 x86/vsmp: Use hypervisor layer for initialization [0.00] tsc: Detected 3200.098 MHz processor [0.00] [ cut here ] [0.00] WARNING: at /c/kernel-tests/src/tip/arch/x86/kernel/vsmp_64.c:158 is_vsmp_box+0xa1/0xb0() [0.00] Hardware name: Bochs [0.00] Pid: 0, comm: swapper/0 Not tainted 3.6.0-rc2-01612-g595b3f3 #292 [0.00] Call Trace: [0.00] [8105a12a] ? warn_slowpath_common+0x7a/0xb0 [0.00] [810339f1] ? is_vsmp_box+0xa1/0xb0 [0.00] [818125d5] ? apic_is_clustered_box+0x34/0x4c [0.00] [8180baa4] ? unsynchronized_tsc+0x23/0x71 [0.00] [81f8330c] ? tsc_init+0xc2/0xed [0.00] [81f7cc0d] ? start_kernel+0x3fd/0x47a [0.00] [81f7c627] ? repair_env_string+0x5b/0x5b [0.00] [81f7c436] ? x86_64_start_kernel+0x105/0x114 If another hypervisor is detected, vsmp's detect callback will not be called, triggering this warning. This commit is is no longer in tip for other reasons, but this issue will be addressed in the next revision of this patch. Thanks, Ido. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
