2018-03-28 5:15 GMT+08:00 kbuild test robot <lkp@xxxxxxxxx>: > Hi Wanpeng, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on kvm/linux-next] > [also build test WARNING on next-20180327] > [cannot apply to v4.16-rc7] > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > url: https://github.com/0day-ci/linux/commits/Wanpeng-Li/KVM-X86-Add-Force-Emulation-Prefix-for-emulate-the-next-instruction/20180328-025804 > base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next > reproduce: > # apt-get install sparse > make ARCH=x86_64 allmodconfig > make C=1 CF=-D__CHECK_ENDIAN__ > > > sparse warnings: (new ones prefixed by >>) > >>> arch/x86/kvm/x86.c:149:20: sparse: symbol 'force_emulation_prefix' was not declared. Should it be static? > arch/x86/kvm/x86.c:2196:38: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const [noderef] <asn:1>*<noident> @@ got d const [noderef] <asn:1>*<noident> @@ > arch/x86/kvm/x86.c:2196:38: expected void const [noderef] <asn:1>*<noident> > arch/x86/kvm/x86.c:2196:38: got unsigned char [usertype] * > arch/x86/kvm/x86.c:7911:5: sparse: symbol 'kvm_valid_sregs' was not declared. Should it be static? > arch/x86/kvm/x86.c:8786:16: sparse: incompatible types in comparison expression (different address spaces) > arch/x86/include/asm/paravirt.h:783:9: sparse: context imbalance in 'vcpu_enter_guest' - unexpected unlock > > Please review and possibly fold the followup patch. Thanks for the report, I will fix it in the next version. Regards, Wanpeng Li
