summaryrefslogtreecommitdiffstats
path: root/.cocciconfig
diff options
context:
space:
mode:
authorTony Luck <tony.luck@intel.com>2017-05-23 08:06:03 +0800
committerBorislav Petkov <bp@suse.de>2017-05-25 11:47:11 +0200
commit7fd562b75d7752ed50c61d65f27b558cd93a359b (patch)
treed9ec3e7a013a19aa68e567fad858e8f940fefe71 /.cocciconfig
parent00cf50d90a99fac96644078f40c88a7ad43fb71c (diff)
downloadop-kernel-dev-7fd562b75d7752ed50c61d65f27b558cd93a359b.zip
op-kernel-dev-7fd562b75d7752ed50c61d65f27b558cd93a359b.tar.gz
EDAC, sb_edac: Don't use "Socket#" in the memory controller name
EDAC assigns logical memory controller numbers in the order that we find memory controllers, which depends on which PCI bus they are on. Some systems end up with MC0 on socket0, others (e.g Haswell) have MC0 on socket3. All this is made more confusing for users because we use the string "Socket" while generating names for memory controllers, but the number that we attach there is the memory controller number. E.g. EDAC MC0: Giving out device to module sbridge_edac.c controller Haswell Socket#0: DEV 0000:ff:12.0 (INTERRUPT) Change the names to say "SrcID#%d" (where the number we use is read from the h/w associated with the memory controller instead of some logical number internal to the EDAC driver). New message: EDAC MC0: Giving out device to module sbridge_edac.c controller Haswell SrcID#3: DEV 0000:ff:12.0 (INTERRUPT) Reported-by: Andrey Korolyov <andrey@xdel.ru> Reported-by: Patrick Geary <patrickg@supermicro.com> Signed-off-by: Tony Luck <tony.luck@intel.com> Cc: linux-edac <linux-edac@vger.kernel.org> Link: http://lkml.kernel.org/r/20170523000603.87748-1-qiuxu.zhuo@intel.com Signed-off-by: Borislav Petkov <bp@suse.de>
Diffstat (limited to '.cocciconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud