diff options
author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-04-16 13:04:46 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-05-28 19:10:59 -0300 |
commit | 982216a4290543fe73ae4f0a156f3d7906bd9b73 (patch) | |
tree | 0555488d5bc70a88ea5a89ccb22a24537ad97091 /drivers/edac | |
parent | 93e4fe64ece4eccf0ff4ac69bceb389290b8ab7c (diff) | |
download | blackbird-op-linux-982216a4290543fe73ae4f0a156f3d7906bd9b73.tar.gz blackbird-op-linux-982216a4290543fe73ae4f0a156f3d7906bd9b73.zip |
edac.h: Add generic layers for describing a memory location
The edac core were written with the idea that memory controllers
are able to directly access csrows, and that the channels are
used inside a csrows select.
This is not true for FB-DIMM and RAMBUS memory controllers.
Also, some recent advanced memory controllers don't present a per-csrows
view. Instead, they view memories as DIMMs, instead of ranks, accessed
via csrow/channel.
So, changes are needed in order to allow the EDAC core to
work with all types of architectures.
In preparation for handling non-csrows based memory controllers,
add some memory structs and a macro:
enum hw_event_mc_err_type: describes the type of error
(corrected, uncorrected, fatal)
To be used by the new edac_mc_handle_error function;
enum edac_mc_layer: describes the type of a given memory
architecture layer (branch, channel, slot, csrow).
struct edac_mc_layer: describes the properties of a memory
layer (type, size, and if the layer
will be used on a virtual csrow.
EDAC_DIMM_PTR() - as the number of layers can vary from 1 to 3,
this macro converts from an address with up to 3 layers into
a linear address.
Reviewed-by: Borislav Petkov <bp@amd64.org>
Cc: Doug Thompson <norsk5@yahoo.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/edac')
0 files changed, 0 insertions, 0 deletions