subject:"\[LKP\] \[lkp\] \[x86 tsc\] 19fa5e7364\: WARNING\: CPU\: 0 PID\: 0 at arch\/x86\/mm\/extable.c\:50 ex_handler_rdmsr

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

2016-06-21 21:59 GMT+08:00 Wanpeng Li :
> Hi Paolo,
> 2016-06-21 18:24 GMT+08:00 Wanpeng Li :
>> 2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>>>
>>>
>>> On 21/06/2016 08:08, Wanpeng Li wrote:
 Cc KVM ML, Paolo, Radim,
>> FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  -append 'root=/dev/ram0 user=lkp 
>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>> branch=internal-eywa/master 
>> commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  max_uptime=600 
>> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
>> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
>> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
>> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
>> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
>> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
>> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot 
>> -watchdog i6300esb -rtc base=localtime -drive 
>> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
>> -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
>> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
>> none -monitor null
>>
> This  problem was caused due to kvm does not support 
> MSR_PLATFORM_INFO(0xce),
> according to Wanpeng's feedback.
>
> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
> might have to use
> rdmsr_safe instead.

 There is a thread discussed this before
 https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
 be simple emulation.

 Ping Paolo, Radim. :)
>>>
>>> rdmsr_safe must be used instead.  I'll prepare a patch.
>>
>> Actually I have such a patch on hand under testing, I will send out soon. :)
>
> I have a temporal patch as below, it seems that guest tsc(~300MHz) is
> still not correct and guest kernel panic during boot w/ message
> "MP-BIOS bug: 8254 timer not connect to IO-APIC, kernel-panic - not
> syncing: IOAPIC + timer doesn't work" etc. Any proposal to improve my
> patch is a great appreciated. :) The patch is against x86 branch on
> Len Brown's tree. And try to fix this commit:
> https://git.kernel.org/cgit/linux/kernel/git/lenb/linux.git/commit/?h=x86=fc141535ad8a67fd58623289c04e35465e2a07f2
>
> 
>
> From 8033ae4c7e44d6bfe26642b151de03c613125066 Mon Sep 17 00:00:00 2001
> From: Wanpeng Li 
> Date: Tue, 21 Jun 2016 19:41:12 +0800
> Subject: [PATCH] x86: fix rdmsr MSR_PLATFORM_INFO unsafe warning in kvm guest
>
> From: Wanpeng Li 
>
> [ cut here ]
> WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50
> ex_handler_rdmsr_unsafe+0x6a/0x70
> unchecked MSR access error: RDMSR from 0xce
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc3+ #1
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
>   81c03ce0 813b3eae 81c03d30
>   81c03d20 81067181 00320001
>  81c03df8 8179676c  81fcd2c0
> Call Trace:
>  dump_stack+0x67/0x99
>  __warn+0xd1/0xf0
>  warn_slowpath_fmt+0x4f/0x60
>  ex_handler_rdmsr_unsafe+0x6a/0x70
>  fixup_exception+0x39/0x50
>  do_general_protection+0x93/0x1b0
>  general_protection+0x22/0x30
>  ? cpu_khz_from_msr+0xd8/0x1c0
>  native_calibrate_cpu+0x30/0x5b0
>  tsc_init+0x2b/0x297
>  x86_late_time_init+0xf/0x11
>  start_kernel+0x398/0x451
>  ? set_init_arg+0x55/0x55
>  x86_64_start_reservations+0x2f/0x31
>  x86_64_start_kernel+0xea/0xed
>
> After commit (fc141535ad8 : "x86 tsc_msr: Extend to include Intel Core
> Architecture"),
> rdmsr MSR_PLATFORM_INFO is used to get maximum non-turbo ratio for
> recent Intel Core
> Architecture which results in kvm guest rdmsr unsafe warning.
>
> As Radim pointed out before:
>
> | MSR_PLATFORM_INFO: Intel changes it from family to family and there is
> | no obvious overlap or default.  If we picked 0 (any other fixed value),
> | then the guest would have to know that 0

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

2016-06-21 21:59 GMT+08:00 Wanpeng Li :
> Hi Paolo,
> 2016-06-21 18:24 GMT+08:00 Wanpeng Li :
>> 2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>>>
>>>
>>> On 21/06/2016 08:08, Wanpeng Li wrote:
 Cc KVM ML, Paolo, Radim,
>> FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  -append 'root=/dev/ram0 user=lkp 
>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>> branch=internal-eywa/master 
>> commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  max_uptime=600 
>> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
>> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
>> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
>> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
>> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
>> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
>> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot 
>> -watchdog i6300esb -rtc base=localtime -drive 
>> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
>> -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
>> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
>> none -monitor null
>>
> This  problem was caused due to kvm does not support 
> MSR_PLATFORM_INFO(0xce),
> according to Wanpeng's feedback.
>
> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
> might have to use
> rdmsr_safe instead.

 There is a thread discussed this before
 https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
 be simple emulation.

 Ping Paolo, Radim. :)
>>>
>>> rdmsr_safe must be used instead.  I'll prepare a patch.
>>
>> Actually I have such a patch on hand under testing, I will send out soon. :)
>
> I have a temporal patch as below, it seems that guest tsc(~300MHz) is
> still not correct and guest kernel panic during boot w/ message
> "MP-BIOS bug: 8254 timer not connect to IO-APIC, kernel-panic - not
> syncing: IOAPIC + timer doesn't work" etc. Any proposal to improve my
> patch is a great appreciated. :) The patch is against x86 branch on
> Len Brown's tree. And try to fix this commit:
> https://git.kernel.org/cgit/linux/kernel/git/lenb/linux.git/commit/?h=x86=fc141535ad8a67fd58623289c04e35465e2a07f2
>
> 
>
> From 8033ae4c7e44d6bfe26642b151de03c613125066 Mon Sep 17 00:00:00 2001
> From: Wanpeng Li 
> Date: Tue, 21 Jun 2016 19:41:12 +0800
> Subject: [PATCH] x86: fix rdmsr MSR_PLATFORM_INFO unsafe warning in kvm guest
>
> From: Wanpeng Li 
>
> [ cut here ]
> WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50
> ex_handler_rdmsr_unsafe+0x6a/0x70
> unchecked MSR access error: RDMSR from 0xce
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc3+ #1
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
>   81c03ce0 813b3eae 81c03d30
>   81c03d20 81067181 00320001
>  81c03df8 8179676c  81fcd2c0
> Call Trace:
>  dump_stack+0x67/0x99
>  __warn+0xd1/0xf0
>  warn_slowpath_fmt+0x4f/0x60
>  ex_handler_rdmsr_unsafe+0x6a/0x70
>  fixup_exception+0x39/0x50
>  do_general_protection+0x93/0x1b0
>  general_protection+0x22/0x30
>  ? cpu_khz_from_msr+0xd8/0x1c0
>  native_calibrate_cpu+0x30/0x5b0
>  tsc_init+0x2b/0x297
>  x86_late_time_init+0xf/0x11
>  start_kernel+0x398/0x451
>  ? set_init_arg+0x55/0x55
>  x86_64_start_reservations+0x2f/0x31
>  x86_64_start_kernel+0xea/0xed
>
> After commit (fc141535ad8 : "x86 tsc_msr: Extend to include Intel Core
> Architecture"),
> rdmsr MSR_PLATFORM_INFO is used to get maximum non-turbo ratio for
> recent Intel Core
> Architecture which results in kvm guest rdmsr unsafe warning.
>
> As Radim pointed out before:
>
> | MSR_PLATFORM_INFO: Intel changes it from family to family and there is
> | no obvious overlap or default.  If we picked 0 (any other fixed value),
> | then the guest would have to know that 0 doesn't mean that
> | MSR_PLATFORM_INFO returned 0, but that KVM doesn't emulate this MSR and
> | the value cannot

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

Hi Paolo,
2016-06-21 18:24 GMT+08:00 Wanpeng Li :
> 2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>>
>>
>> On 21/06/2016 08:08, Wanpeng Li wrote:
>>> Cc KVM ML, Paolo, Radim,
> FYI, raw QEMU command line is:
>
> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  -append 'root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
> branch=internal-eywa/master 
> commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  max_uptime=600 
> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot 
> -watchdog i6300esb -rtc base=localtime -drive 
> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
> -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
> none -monitor null
>
 This  problem was caused due to kvm does not support 
 MSR_PLATFORM_INFO(0xce),
 according to Wanpeng's feedback.

 Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
 might have to use
 rdmsr_safe instead.
>>>
>>> There is a thread discussed this before
>>> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
>>> be simple emulation.
>>>
>>> Ping Paolo, Radim. :)
>>
>> rdmsr_safe must be used instead.  I'll prepare a patch.
>
> Actually I have such a patch on hand under testing, I will send out soon. :)

I have a temporal patch as below, it seems that guest tsc(~300MHz) is
still not correct and guest kernel panic during boot w/ message
"MP-BIOS bug: 8254 timer not connect to IO-APIC, kernel-panic - not
syncing: IOAPIC + timer doesn't work" etc. Any proposal to improve my
patch is a great appreciated. :) The patch is against x86 branch on
Len Brown's tree. And try to fix this commit:
https://git.kernel.org/cgit/linux/kernel/git/lenb/linux.git/commit/?h=x86=fc141535ad8a67fd58623289c04e35465e2a07f2



>From 8033ae4c7e44d6bfe26642b151de03c613125066 Mon Sep 17 00:00:00 2001
From: Wanpeng Li 
Date: Tue, 21 Jun 2016 19:41:12 +0800
Subject: [PATCH] x86: fix rdmsr MSR_PLATFORM_INFO unsafe warning in kvm guest

From: Wanpeng Li 

[ cut here ]
WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50
ex_handler_rdmsr_unsafe+0x6a/0x70
unchecked MSR access error: RDMSR from 0xce
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc3+ #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
  81c03ce0 813b3eae 81c03d30
  81c03d20 81067181 00320001
 81c03df8 8179676c  81fcd2c0
Call Trace:
 dump_stack+0x67/0x99
 __warn+0xd1/0xf0
 warn_slowpath_fmt+0x4f/0x60
 ex_handler_rdmsr_unsafe+0x6a/0x70
 fixup_exception+0x39/0x50
 do_general_protection+0x93/0x1b0
 general_protection+0x22/0x30
 ? cpu_khz_from_msr+0xd8/0x1c0
 native_calibrate_cpu+0x30/0x5b0
 tsc_init+0x2b/0x297
 x86_late_time_init+0xf/0x11
 start_kernel+0x398/0x451
 ? set_init_arg+0x55/0x55
 x86_64_start_reservations+0x2f/0x31
 x86_64_start_kernel+0xea/0xed

After commit (fc141535ad8 : "x86 tsc_msr: Extend to include Intel Core
Architecture"),
rdmsr MSR_PLATFORM_INFO is used to get maximum non-turbo ratio for
recent Intel Core
Architecture which results in kvm guest rdmsr unsafe warning.

As Radim pointed out before:

| MSR_PLATFORM_INFO: Intel changes it from family to family and there is
| no obvious overlap or default.  If we picked 0 (any other fixed value),
| then the guest would have to know that 0 doesn't mean that
| MSR_PLATFORM_INFO returned 0, but that KVM doesn't emulate this MSR and
| the value cannot be used.  This is very similar to handling a #GP in the
| guest, but also has a disadvantage, because KVM

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

Hi Paolo,
2016-06-21 18:24 GMT+08:00 Wanpeng Li :
> 2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>>
>>
>> On 21/06/2016 08:08, Wanpeng Li wrote:
>>> Cc KVM ML, Paolo, Radim,
> FYI, raw QEMU command line is:
>
> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  -append 'root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
> branch=internal-eywa/master 
> commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  max_uptime=600 
> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
> panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot 
> -watchdog i6300esb -rtc base=localtime -drive 
> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
> -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
> none -monitor null
>
 This  problem was caused due to kvm does not support 
 MSR_PLATFORM_INFO(0xce),
 according to Wanpeng's feedback.

 Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
 might have to use
 rdmsr_safe instead.
>>>
>>> There is a thread discussed this before
>>> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
>>> be simple emulation.
>>>
>>> Ping Paolo, Radim. :)
>>
>> rdmsr_safe must be used instead.  I'll prepare a patch.
>
> Actually I have such a patch on hand under testing, I will send out soon. :)

I have a temporal patch as below, it seems that guest tsc(~300MHz) is
still not correct and guest kernel panic during boot w/ message
"MP-BIOS bug: 8254 timer not connect to IO-APIC, kernel-panic - not
syncing: IOAPIC + timer doesn't work" etc. Any proposal to improve my
patch is a great appreciated. :) The patch is against x86 branch on
Len Brown's tree. And try to fix this commit:
https://git.kernel.org/cgit/linux/kernel/git/lenb/linux.git/commit/?h=x86=fc141535ad8a67fd58623289c04e35465e2a07f2



>From 8033ae4c7e44d6bfe26642b151de03c613125066 Mon Sep 17 00:00:00 2001
From: Wanpeng Li 
Date: Tue, 21 Jun 2016 19:41:12 +0800
Subject: [PATCH] x86: fix rdmsr MSR_PLATFORM_INFO unsafe warning in kvm guest

From: Wanpeng Li 

[ cut here ]
WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50
ex_handler_rdmsr_unsafe+0x6a/0x70
unchecked MSR access error: RDMSR from 0xce
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc3+ #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
  81c03ce0 813b3eae 81c03d30
  81c03d20 81067181 00320001
 81c03df8 8179676c  81fcd2c0
Call Trace:
 dump_stack+0x67/0x99
 __warn+0xd1/0xf0
 warn_slowpath_fmt+0x4f/0x60
 ex_handler_rdmsr_unsafe+0x6a/0x70
 fixup_exception+0x39/0x50
 do_general_protection+0x93/0x1b0
 general_protection+0x22/0x30
 ? cpu_khz_from_msr+0xd8/0x1c0
 native_calibrate_cpu+0x30/0x5b0
 tsc_init+0x2b/0x297
 x86_late_time_init+0xf/0x11
 start_kernel+0x398/0x451
 ? set_init_arg+0x55/0x55
 x86_64_start_reservations+0x2f/0x31
 x86_64_start_kernel+0xea/0xed

After commit (fc141535ad8 : "x86 tsc_msr: Extend to include Intel Core
Architecture"),
rdmsr MSR_PLATFORM_INFO is used to get maximum non-turbo ratio for
recent Intel Core
Architecture which results in kvm guest rdmsr unsafe warning.

As Radim pointed out before:

| MSR_PLATFORM_INFO: Intel changes it from family to family and there is
| no obvious overlap or default.  If we picked 0 (any other fixed value),
| then the guest would have to know that 0 doesn't mean that
| MSR_PLATFORM_INFO returned 0, but that KVM doesn't emulate this MSR and
| the value cannot be used.  This is very similar to handling a #GP in the
| guest, but also has a disadvantage, because KVM cannot say that
| MSR_PLATFORM_INFO is 0.  Simple emulation is not possible.

This patch fix

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>
>
> On 21/06/2016 08:08, Wanpeng Li wrote:
>> Cc KVM ML, Paolo, Radim,
 FYI, raw QEMU command line is:

 qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
 /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
  -append 'root=/dev/ram0 user=lkp 
 job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
 branch=internal-eywa/master 
 commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
  max_uptime=600 
 RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
 apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
 ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
 /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
 e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot -watchdog 
 i6300esb -rtc base=localtime -drive 
 file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
 -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
 file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
 none -monitor null

>>> This  problem was caused due to kvm does not support 
>>> MSR_PLATFORM_INFO(0xce),
>>> according to Wanpeng's feedback.
>>>
>>> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
>>> might have to use
>>> rdmsr_safe instead.
>>
>> There is a thread discussed this before
>> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
>> be simple emulation.
>>
>> Ping Paolo, Radim. :)
>
> rdmsr_safe must be used instead.  I'll prepare a patch.

Actually I have such a patch on hand under testing, I will send out soon. :)

Regards,
Wanpeng Li

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>
>
> On 21/06/2016 08:08, Wanpeng Li wrote:
>> Cc KVM ML, Paolo, Radim,
 FYI, raw QEMU command line is:

 qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
 /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
  -append 'root=/dev/ram0 user=lkp 
 job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
 branch=internal-eywa/master 
 commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
  max_uptime=600 
 RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
 apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 
 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
 ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
 /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
 e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot -watchdog 
 i6300esb -rtc base=localtime -drive 
 file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio 
 -pidfile /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
 file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
 none -monitor null

>>> This  problem was caused due to kvm does not support 
>>> MSR_PLATFORM_INFO(0xce),
>>> according to Wanpeng's feedback.
>>>
>>> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
>>> might have to use
>>> rdmsr_safe instead.
>>
>> There is a thread discussed this before
>> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
>> be simple emulation.
>>
>> Ping Paolo, Radim. :)
>
> rdmsr_safe must be used instead.  I'll prepare a patch.

Actually I have such a patch on hand under testing, I will send out soon. :)

Regards,
Wanpeng Li

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Paolo Bonzini



On 21/06/2016 08:08, Wanpeng Li wrote:
> Cc KVM ML, Paolo, Radim,
>>> FYI, raw QEMU command line is:
>>>
>>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>>  -append 'root=/dev/ram0 user=lkp 
>>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>>> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>>> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>>  max_uptime=600 
>>> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>>>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
>>> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 
>>> softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
>>> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
>>> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
>>> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
>>> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot -watchdog 
>>> i6300esb -rtc base=localtime -drive 
>>> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio -pidfile 
>>> /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
>>> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
>>> none -monitor null
>>>
>> This  problem was caused due to kvm does not support MSR_PLATFORM_INFO(0xce),
>> according to Wanpeng's feedback.
>>
>> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
>> might have to use
>> rdmsr_safe instead.
> 
> There is a thread discussed this before
> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
> be simple emulation.
> 
> Ping Paolo, Radim. :)

rdmsr_safe must be used instead.  I'll prepare a patch.

Paolo

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Paolo Bonzini



On 21/06/2016 08:08, Wanpeng Li wrote:
> Cc KVM ML, Paolo, Radim,
>>> FYI, raw QEMU command line is:
>>>
>>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>>  -append 'root=/dev/ram0 user=lkp 
>>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>>> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>>> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>>  max_uptime=600 
>>> RESULT_ROOT=/result/boot/1/vm-kbuild-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/0
>>>  LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug 
>>> apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 
>>> softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 
>>> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw 
>>> ip=vm-kbuild-yocto-x86_64-32::dhcp drbd.minor_count=8'  -initrd 
>>> /fs/sdh1/initrd-vm-kbuild-yocto-x86_64-32 -m 320 -smp 1 -device 
>>> e1000,netdev=net0 -netdev user,id=net0 -boot order=nc -no-reboot -watchdog 
>>> i6300esb -rtc base=localtime -drive 
>>> file=/fs/sdh1/disk0-vm-kbuild-yocto-x86_64-32,media=disk,if=virtio -pidfile 
>>> /dev/shm/kboot/pid-vm-kbuild-yocto-x86_64-32 -serial 
>>> file:/dev/shm/kboot/serial-vm-kbuild-yocto-x86_64-32 -daemonize -display 
>>> none -monitor null
>>>
>> This  problem was caused due to kvm does not support MSR_PLATFORM_INFO(0xce),
>> according to Wanpeng's feedback.
>>
>> Hi Wanpeng, is it possible for kvm to simulate this MSR, otherwise we
>> might have to use
>> rdmsr_safe instead.
> 
> There is a thread discussed this before
> https://patchwork.kernel.org/patch/8833021/, MSR_PLATFORM_INFO can't
> be simple emulation.
> 
> Ping Paolo, Radim. :)

rdmsr_safe must be used instead.  I'll prepare a patch.

Paolo

Re: Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

Cc KVM ML, Paolo, Radim,
> Hi,
>
> On Mon, Jun 20, 2016 at 3:31 PM, kernel test robot
>  wrote:
>>
>> FYI, we noticed the following commit:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git x86
>> commit 19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 ("x86 tsc: enumerate SKL 
>> cpu_khz and tsc_khz via CPUID")
>>
>>
>> on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 
>> -enable-kvm -cpu SandyBridge with 320M memory
>>
>> caused below changes:
>>
>>
>> +--+++
>> |  | 
>> cc50dc7f73 | 19fa5e7364 |
>> +--+++
>> | boot_successes   | 0   
>>| 0  |
>> | boot_failures| 10  
>>| 12 |
>> | invoked_oom-killer:gfp_mask=0x   | 10  
>>| 10 |
>> | Mem-Info | 10  
>>| 10 |
>> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 10  
>>| 10 |
>> | backtrace:btrfs_test_extent_io   | 10  
>>| 10 |
>> | backtrace:init_btrfs_fs  | 10  
>>| 10 |
>> | backtrace:kernel_init_freeable   | 10  
>>| 10 |
>> | WARNING:at_arch/x86/mm/extable.c:#ex_handler_rdmsr_unsafe| 0   
>>| 10 |
>> | backtrace:native_calibrate_cpu   | 0   
>>| 10 |
>> | backtrace:tsc_init   | 0   
>>| 10 |
>> | backtrace:x86_late_time_init | 0   
>>| 10 |
>> +--+++
>>
>>
>>
>> [0.00] clocksource: hpet: mask: 0x max_cycles: 0x, 
>> max_idle_ns: 19112604467 ns
>> [0.00] hpet clockevent registered
>> [0.00] [ cut here ]
>> [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 
>> ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00] unchecked MSR access error: RDMSR from 0xce
>> [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 
>> 4.7.0-rc3-9-g19fa5e7 #1
>> [0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
>> Debian-1.8.2-1 04/01/2014
>> [0.00]   83203c38 816da89d 
>> 83203c88
>> [0.00]   82e71808 8104e8c2 
>> 83203c78
>> [0.00]  810b796b 00328453b4a0 82e71808 
>> 0032
>> [0.00] Call Trace:
>> [0.00]  [] dump_stack+0x83/0xb6
>> [0.00]  [] ? ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00]  [] __warn+0x10b/0x130
>> [0.00]  [] warn_slowpath_fmt+0x63/0x70
>> [0.00]  [] ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00]  [] fixup_exception+0x46/0x60
>> [0.00]  [] do_general_protection+0x7b/0x150
>> [0.00]  [] general_protection+0x28/0x30
>> [0.00]  [] ? native_read_msr+0x6/0x20
>> [0.00]  [] cpu_khz_from_msr+0xf1/0x150
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] native_calibrate_cpu+0x85/0x5b0
>> [0.00]  [] ? native_restore_fl+0x6/0x10
>> [0.00]  [] ? __setup_irq+0x196/0x750
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] tsc_init+0x42/0x3c3
>> [0.00]  [] ? setup_irq+0x6f/0xc0
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] x86_late_time_init+0xf/0x11
>> [0.00]  [] ? x86_late_time_init+0xf/0x11
>> [0.00]  [] start_kernel+0x3f3/0x4b1
>> [0.00]  [] ? early_idt_handler_array+0x120/0x120
>> [0.00]  [] x86_64_start_reservations+0x2f/0x31
>> [0.00]  [] x86_64_start_kernel+0xe6/0xf3
>> [0.00] ---[ end trace 7c0d92684f22f4ac ]---
>> [0.00] tsc: Fast TSC calibration using PIT
>>
>>
>> FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  -append 'root=/dev/ram0 user=lkp 
>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>>

Re: Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-21 Thread Wanpeng Li

Cc KVM ML, Paolo, Radim,
> Hi,
>
> On Mon, Jun 20, 2016 at 3:31 PM, kernel test robot
>  wrote:
>>
>> FYI, we noticed the following commit:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git x86
>> commit 19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 ("x86 tsc: enumerate SKL 
>> cpu_khz and tsc_khz via CPUID")
>>
>>
>> on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 
>> -enable-kvm -cpu SandyBridge with 320M memory
>>
>> caused below changes:
>>
>>
>> +--+++
>> |  | 
>> cc50dc7f73 | 19fa5e7364 |
>> +--+++
>> | boot_successes   | 0   
>>| 0  |
>> | boot_failures| 10  
>>| 12 |
>> | invoked_oom-killer:gfp_mask=0x   | 10  
>>| 10 |
>> | Mem-Info | 10  
>>| 10 |
>> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 10  
>>| 10 |
>> | backtrace:btrfs_test_extent_io   | 10  
>>| 10 |
>> | backtrace:init_btrfs_fs  | 10  
>>| 10 |
>> | backtrace:kernel_init_freeable   | 10  
>>| 10 |
>> | WARNING:at_arch/x86/mm/extable.c:#ex_handler_rdmsr_unsafe| 0   
>>| 10 |
>> | backtrace:native_calibrate_cpu   | 0   
>>| 10 |
>> | backtrace:tsc_init   | 0   
>>| 10 |
>> | backtrace:x86_late_time_init | 0   
>>| 10 |
>> +--+++
>>
>>
>>
>> [0.00] clocksource: hpet: mask: 0x max_cycles: 0x, 
>> max_idle_ns: 19112604467 ns
>> [0.00] hpet clockevent registered
>> [0.00] [ cut here ]
>> [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 
>> ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00] unchecked MSR access error: RDMSR from 0xce
>> [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 
>> 4.7.0-rc3-9-g19fa5e7 #1
>> [0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
>> Debian-1.8.2-1 04/01/2014
>> [0.00]   83203c38 816da89d 
>> 83203c88
>> [0.00]   82e71808 8104e8c2 
>> 83203c78
>> [0.00]  810b796b 00328453b4a0 82e71808 
>> 0032
>> [0.00] Call Trace:
>> [0.00]  [] dump_stack+0x83/0xb6
>> [0.00]  [] ? ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00]  [] __warn+0x10b/0x130
>> [0.00]  [] warn_slowpath_fmt+0x63/0x70
>> [0.00]  [] ex_handler_rdmsr_unsafe+0x72/0x80
>> [0.00]  [] fixup_exception+0x46/0x60
>> [0.00]  [] do_general_protection+0x7b/0x150
>> [0.00]  [] general_protection+0x28/0x30
>> [0.00]  [] ? native_read_msr+0x6/0x20
>> [0.00]  [] cpu_khz_from_msr+0xf1/0x150
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] native_calibrate_cpu+0x85/0x5b0
>> [0.00]  [] ? native_restore_fl+0x6/0x10
>> [0.00]  [] ? __setup_irq+0x196/0x750
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] tsc_init+0x42/0x3c3
>> [0.00]  [] ? setup_irq+0x6f/0xc0
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] ? trap_init+0x22e/0x22e
>> [0.00]  [] x86_late_time_init+0xf/0x11
>> [0.00]  [] ? x86_late_time_init+0xf/0x11
>> [0.00]  [] start_kernel+0x3f3/0x4b1
>> [0.00]  [] ? early_idt_handler_array+0x120/0x120
>> [0.00]  [] x86_64_start_reservations+0x2f/0x31
>> [0.00]  [] x86_64_start_kernel+0xe6/0xf3
>> [0.00] ---[ end trace 7c0d92684f22f4ac ]---
>> [0.00] tsc: Fast TSC calibration using PIT
>>
>>
>> FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
>> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>>  -append 'root=/dev/ram0 user=lkp 
>> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
>> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
>>

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-20 Thread Yu Chen

Hi,

On Mon, Jun 20, 2016 at 3:31 PM, kernel test robot
 wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git x86
> commit 19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 ("x86 tsc: enumerate SKL 
> cpu_khz and tsc_khz via CPUID")
>
>
> on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 
> -enable-kvm -cpu SandyBridge with 320M memory
>
> caused below changes:
>
>
> +--+++
> |  | 
> cc50dc7f73 | 19fa5e7364 |
> +--+++
> | boot_successes   | 0
>   | 0  |
> | boot_failures| 10   
>   | 12 |
> | invoked_oom-killer:gfp_mask=0x   | 10   
>   | 10 |
> | Mem-Info | 10   
>   | 10 |
> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 10   
>   | 10 |
> | backtrace:btrfs_test_extent_io   | 10   
>   | 10 |
> | backtrace:init_btrfs_fs  | 10   
>   | 10 |
> | backtrace:kernel_init_freeable   | 10   
>   | 10 |
> | WARNING:at_arch/x86/mm/extable.c:#ex_handler_rdmsr_unsafe| 0
>   | 10 |
> | backtrace:native_calibrate_cpu   | 0
>   | 10 |
> | backtrace:tsc_init   | 0
>   | 10 |
> | backtrace:x86_late_time_init | 0
>   | 10 |
> +--+++
>
>
>
> [0.00] clocksource: hpet: mask: 0x max_cycles: 0x, 
> max_idle_ns: 19112604467 ns
> [0.00] hpet clockevent registered
> [0.00] [ cut here ]
> [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 
> ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00] unchecked MSR access error: RDMSR from 0xce
> [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 
> 4.7.0-rc3-9-g19fa5e7 #1
> [0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
> Debian-1.8.2-1 04/01/2014
> [0.00]   83203c38 816da89d 
> 83203c88
> [0.00]   82e71808 8104e8c2 
> 83203c78
> [0.00]  810b796b 00328453b4a0 82e71808 
> 0032
> [0.00] Call Trace:
> [0.00]  [] dump_stack+0x83/0xb6
> [0.00]  [] ? ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00]  [] __warn+0x10b/0x130
> [0.00]  [] warn_slowpath_fmt+0x63/0x70
> [0.00]  [] ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00]  [] fixup_exception+0x46/0x60
> [0.00]  [] do_general_protection+0x7b/0x150
> [0.00]  [] general_protection+0x28/0x30
> [0.00]  [] ? native_read_msr+0x6/0x20
> [0.00]  [] cpu_khz_from_msr+0xf1/0x150
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] native_calibrate_cpu+0x85/0x5b0
> [0.00]  [] ? native_restore_fl+0x6/0x10
> [0.00]  [] ? __setup_irq+0x196/0x750
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] tsc_init+0x42/0x3c3
> [0.00]  [] ? setup_irq+0x6f/0xc0
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] x86_late_time_init+0xf/0x11
> [0.00]  [] ? x86_late_time_init+0xf/0x11
> [0.00]  [] start_kernel+0x3f3/0x4b1
> [0.00]  [] ? early_idt_handler_array+0x120/0x120
> [0.00]  [] x86_64_start_reservations+0x2f/0x31
> [0.00]  [] x86_64_start_kernel+0xe6/0xf3
> [0.00] ---[ end trace 7c0d92684f22f4ac ]---
> [0.00] tsc: Fast TSC calibration using PIT
>
>
> FYI, raw QEMU command line is:
>
> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  -append 'root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  max_uptime=600 
>

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

2016-06-20 Thread Yu Chen

Hi,

On Mon, Jun 20, 2016 at 3:31 PM, kernel test robot
 wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git x86
> commit 19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 ("x86 tsc: enumerate SKL 
> cpu_khz and tsc_khz via CPUID")
>
>
> on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 
> -enable-kvm -cpu SandyBridge with 320M memory
>
> caused below changes:
>
>
> +--+++
> |  | 
> cc50dc7f73 | 19fa5e7364 |
> +--+++
> | boot_successes   | 0
>   | 0  |
> | boot_failures| 10   
>   | 12 |
> | invoked_oom-killer:gfp_mask=0x   | 10   
>   | 10 |
> | Mem-Info | 10   
>   | 10 |
> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 10   
>   | 10 |
> | backtrace:btrfs_test_extent_io   | 10   
>   | 10 |
> | backtrace:init_btrfs_fs  | 10   
>   | 10 |
> | backtrace:kernel_init_freeable   | 10   
>   | 10 |
> | WARNING:at_arch/x86/mm/extable.c:#ex_handler_rdmsr_unsafe| 0
>   | 10 |
> | backtrace:native_calibrate_cpu   | 0
>   | 10 |
> | backtrace:tsc_init   | 0
>   | 10 |
> | backtrace:x86_late_time_init | 0
>   | 10 |
> +--+++
>
>
>
> [0.00] clocksource: hpet: mask: 0x max_cycles: 0x, 
> max_idle_ns: 19112604467 ns
> [0.00] hpet clockevent registered
> [0.00] [ cut here ]
> [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 
> ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00] unchecked MSR access error: RDMSR from 0xce
> [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 
> 4.7.0-rc3-9-g19fa5e7 #1
> [0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
> Debian-1.8.2-1 04/01/2014
> [0.00]   83203c38 816da89d 
> 83203c88
> [0.00]   82e71808 8104e8c2 
> 83203c78
> [0.00]  810b796b 00328453b4a0 82e71808 
> 0032
> [0.00] Call Trace:
> [0.00]  [] dump_stack+0x83/0xb6
> [0.00]  [] ? ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00]  [] __warn+0x10b/0x130
> [0.00]  [] warn_slowpath_fmt+0x63/0x70
> [0.00]  [] ex_handler_rdmsr_unsafe+0x72/0x80
> [0.00]  [] fixup_exception+0x46/0x60
> [0.00]  [] do_general_protection+0x7b/0x150
> [0.00]  [] general_protection+0x28/0x30
> [0.00]  [] ? native_read_msr+0x6/0x20
> [0.00]  [] cpu_khz_from_msr+0xf1/0x150
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] native_calibrate_cpu+0x85/0x5b0
> [0.00]  [] ? native_restore_fl+0x6/0x10
> [0.00]  [] ? __setup_irq+0x196/0x750
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] tsc_init+0x42/0x3c3
> [0.00]  [] ? setup_irq+0x6f/0xc0
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] ? trap_init+0x22e/0x22e
> [0.00]  [] x86_late_time_init+0xf/0x11
> [0.00]  [] ? x86_late_time_init+0xf/0x11
> [0.00]  [] start_kernel+0x3f3/0x4b1
> [0.00]  [] ? early_idt_handler_array+0x120/0x120
> [0.00]  [] x86_64_start_reservations+0x2f/0x31
> [0.00]  [] x86_64_start_kernel+0xe6/0xf3
> [0.00] ---[ end trace 7c0d92684f22f4ac ]---
> [0.00] tsc: Fast TSC calibration using PIT
>
>
> FYI, raw QEMU command line is:
>
> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel 
> /pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  -append 'root=/dev/ram0 user=lkp 
> job=/lkp/scheduled/vm-kbuild-yocto-x86_64-32/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-w0-06180628-19fa5e73647fde1e6a7038a8f05cddf4c43f08d3-20160618-25535-h82bax-0.yaml~
>  ARCH=x86_64 kconfig=x86_64-randconfig-w0-06180628 
> branch=internal-eywa/master commit=19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 
> BOOT_IMAGE=/pkg/linux/x86_64-randconfig-w0-06180628/gcc-6/19fa5e73647fde1e6a7038a8f05cddf4c43f08d3/vmlinuz-4.7.0-rc3-9-g19fa5e7
>  max_uptime=600 
>

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

Re: [LKP] [lkp] [x86 tsc] 19fa5e7364: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe+0x72/0x80

12 matches

Site Navigation

Mail list logo

Footer information