diff options
| author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2009-07-09 22:14:35 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-05-10 11:44:50 -0300 |
| commit | e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171 (patch) | |
| tree | 850cc08ec621dea67cdaf8bb5ef03f14ee452815 /include/linux/pci_ids.h | |
| parent | d5381642ab01b084787925acdf26b5524d434476 (diff) | |
| download | kernel_samsung_smdk4412-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.zip kernel_samsung_smdk4412-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.tar.gz kernel_samsung_smdk4412-e9bd2e73793bf0f7fcd8f94b532bb8f5c5b44171.tar.bz2 | |
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 'include/linux/pci_ids.h')
| -rw-r--r-- | include/linux/pci_ids.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h index c5dd099..9d5bfe8 100644 --- a/include/linux/pci_ids.h +++ b/include/linux/pci_ids.h @@ -2548,6 +2548,7 @@ #define PCI_DEVICE_ID_INTEL_I7_MC_CH2_ADDR 0x2c31 #define PCI_DEVICE_ID_INTEL_I7_MC_CH2_RANK 0x2c32 #define PCI_DEVICE_ID_INTEL_I7_MC_CH2_TC 0x2c33 +#define PCI_DEVICE_ID_INTEL_I7_NOCORE 0x2c41 #define PCI_DEVICE_ID_INTEL_82855PM_HB 0x3340 #define PCI_DEVICE_ID_INTEL_IOAT_TBG4 0x3429 #define PCI_DEVICE_ID_INTEL_IOAT_TBG5 0x342a |