summaryrefslogtreecommitdiffstats
path: root/lib/locking-selftest-wlock-softirq.h
diff options
context:
space:
mode:
authorMauro Carvalho Chehab2009-07-10 03:14:35 +0200
committerMauro Carvalho Chehab2010-05-10 16:44:50 +0200
commite9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171 (patch)
tree850cc08ec621dea67cdaf8bb5ef03f14ee452815 /lib/locking-selftest-wlock-softirq.h
parenti7core_edac: Add edac_mce glue (diff)
downloadkernel-qcow2-linux-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.tar.gz
kernel-qcow2-linux-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.tar.xz
kernel-qcow2-linux-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.zip
i7core_edac: Adds write unlock to MC registers
The public Intel Xeon 5500 volume 2 datasheet describes, on page 53, session 2.6.7 a register that can lock/unlock Memory Controller the configuration register, called MC_CFG_CONTROL. Adds support for it in the hope that software error injection would work. With my tests with Xeon 35xx, there's still something missing. With a program that does sequencial bit writes at dev 0.0, sometimes, it produces error injection, after unblocking the MC_CFG_CONTROL (and, sometimes, it just locks my testing machine). I'll try later to discover by trial and error what's the register that solves this issue on Xeon 35xx. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'lib/locking-selftest-wlock-softirq.h')
0 files changed, 0 insertions, 0 deletions