summaryrefslogtreecommitdiffstats
path: root/drivers/ras
diff options
context:
space:
mode:
authorYazen Ghannam <yazen.ghannam@amd.com>2017-06-26 14:35:31 +0200
committerThomas Gleixner <tglx@linutronix.de>2017-06-26 15:58:56 +0200
commite2de64ec52659870b4fdef5bf08f265ce5fe1ccc (patch)
tree28bf8fe0f879a8d1e7fb588a3d5a9cf63501af99 /drivers/ras
parentb867059018a5254cca14450eefb6fb8effa0f6dd (diff)
downloadlinux-e2de64ec52659870b4fdef5bf08f265ce5fe1ccc.tar.gz
linux-e2de64ec52659870b4fdef5bf08f265ce5fe1ccc.tar.bz2
linux-e2de64ec52659870b4fdef5bf08f265ce5fe1ccc.zip
x86/mce: Always save severity in machine_check_poll()
The MCE severity gives a hint as to how to handle the error. The notifier blocks can then use the severity to decide on an action. It's not necessary for machine_check_poll() to filter errors for the notifier chain, since each block will check its own set of conditions before handling an error. Also, there isn't any urgency for machine_check_poll() to make decisions based on severity like in do_machine_check(). If we can assume that a severity is set then we can use it in more notifier blocks. For example, the CEC block could check for a "KEEP" severity rather than checking bits in the status. This isn't possible now since the severity is not set except for "DEFFRRED/UCNA" errors with a valid address. Save the severity since we have it, and let the notifier blocks decide if they want to do anything. Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com> Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/1498074402-98633-1-git-send-email-Yazen.Ghannam@amd.com
Diffstat (limited to 'drivers/ras')
0 files changed, 0 insertions, 0 deletions