diff options
| author | Borislav Petkov <[email protected]> | 2014-10-21 22:19:59 +0200 |
|---|---|---|
| committer | Borislav Petkov <[email protected]> | 2014-10-21 22:28:48 +0200 |
| commit | a3a529d104ec5149fb9a667dce988635941be1ed (patch) | |
| tree | 7be73a235ce379c859e47710b5192316a51de89e /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 69b957583580bf40624553c64d802fefb54199cb (diff) | |
x86, MCE, AMD: Drop software-defined bank in error thresholding
Aravind had the good question about why we're assigning a
software-defined bank when reporting error thresholding errors instead
of simply using the bank which reports the last error causing the
overflow.
Digging through git history, it pointed to
95268664390b ("[PATCH] x86_64: mce_amd support for family 0x10 processors")
which added that functionality. The problem with this, however, is that
tools don't know about software-defined banks and get puzzled. So drop
that K8_MCE_THRESHOLD_BASE and simply use the hw bank reporting the
thresholding interrupt.
Save us a couple of MSR reads while at it.
Reported-by: Aravind Gopalakrishnan <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Borislav Petkov <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions