[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [xen-tip:linux-next 21/23] arch/x86/xen/pmu.c:211:20: sparse: symbol 'xen_amd_read_pmc' was not declared. Should it be static?



tree:   git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip linux-next
head:   0d26d72cab825a0227c8d8e0e42161125b3116fd
commit: 80ef65bb2362fd9eedcb4ec1d41d8a6d0b99dfbb [21/23] xen/PMU: Intercept 
PMU-related MSR and APIC accesses
reproduce:
  # apt-get install sparse
  git checkout 80ef65bb2362fd9eedcb4ec1d41d8a6d0b99dfbb
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   arch/x86/xen/pmu.c:18:1: sparse: symbol '__pcpu_scope_xenpmu_shared' was not 
declared. Should it be static?
>> arch/x86/xen/pmu.c:211:20: sparse: symbol 'xen_amd_read_pmc' was not 
>> declared. Should it be static?
>> arch/x86/xen/pmu.c:220:20: sparse: symbol 'xen_intel_read_pmc' was not 
>> declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.