summaryrefslogtreecommitdiff
path: root/arch/x86/include/asm/amd_nb.h
diff options
context:
space:
mode:
authorYazen Ghannam <Yazen.Ghannam@amd.com>2016-11-16 00:13:53 +0300
committerThomas Gleixner <tglx@linutronix.de>2016-11-16 11:57:11 +0300
commit18807ddb7f88d4ac3797302bafb18143d573e66f (patch)
treed135705d42fe141c570c036f6fbc1ffbc32b2f84 /arch/x86/include/asm/amd_nb.h
parent859af13a103fc99a9a62064ef8f05f7d9ee58609 (diff)
downloadlinux-18807ddb7f88d4ac3797302bafb18143d573e66f.tar.xz
x86/mce/AMD: Reset Threshold Limit after logging error
The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. Signed-off-by: Yazen Ghannam <Yazen.Ghannam@amd.com> Cc: Aravind Gopalakrishnan <aravindksg.lkml@gmail.com> Cc: linux-edac <linux-edac@vger.kernel.org> Cc: x86-ml <x86@kernel.org> Link: http://lkml.kernel.org/r/1479244433-69267-1-git-send-email-Yazen.Ghannam@amd.com Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch/x86/include/asm/amd_nb.h')
0 files changed, 0 insertions, 0 deletions