> Later, we could extend that same behavior to Intel for the common > errors, at least, so that we can dump at least *some* string explaining > what the error is.
s/common errors/architectural errors/ That means we don't need to keep updating for every Xeon that documents some MCi_STATUS.MSCOD bits. Decoding the MCACOD bits will explain which component is involved (cache, bus, memory) and some detail on the type of access. -Tony
