diff options
| author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-10-20 19:18:01 -0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-11-01 10:01:53 -0200 |
| commit | eebf11a0166f011c5945dd30fd1779afca6c964e (patch) | |
| tree | 4d7f4940ca6aff78ef29f7b94c94c176a8c42aae /drivers/edac/Kconfig | |
| parent | 5f032119d6f1cc48d0d1a28b8014f270ca4c4e47 (diff) | |
| download | linux-3.10-eebf11a0166f011c5945dd30fd1779afca6c964e.tar.gz linux-3.10-eebf11a0166f011c5945dd30fd1779afca6c964e.tar.bz2 linux-3.10-eebf11a0166f011c5945dd30fd1779afca6c964e.zip | |
edac: Add an experimental new driver to support Sandy Bridge CPU's
This driver is known to work on mine and Tony's test environments,
using software error injection, and a partial hardware/software
error injection tool.
There's no broader range test yet to double check if the error decoding
logic will actually point to the right DIMM, so use it with care.
More tests are required to be sure that the driver will work on all
different types of memory configurations.
If you're willing to risk using it, I suggest you to enable EDAC debugs
for your test machines, as the debug logs helps to track what's going
inside the driver.
Please feed me with bug reports, if you notice that the driver
is miss-behaving.
Tested-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/edac/Kconfig')
0 files changed, 0 insertions, 0 deletions