aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Trace/intel-pt/TraceIntelPTMultiCpuDecoder.cpp
diff options
context:
space:
mode:
authorKevin Bowling <kbowling@FreeBSD.org>2026-08-12 23:35:43 +0000
committerKevin Bowling <kbowling@FreeBSD.org>2026-08-16 09:43:44 +0000
commit8367882d531313eea68966b07ddf917e39690b77 (patch)
tree92fd4be0ecaa1f736dd80a2fec9634c67fbb417b /lldb/source/Plugins/Trace/intel-pt/TraceIntelPTMultiCpuDecoder.cpp
parent28bbe1d28d6f1e68e2ee3b34686ccb6114c42ca7 (diff)
e1000: Report corrected I350 ECC errorsHEADmain
I350 does not interrupt for corrected internal ECC errors. Instead, the PCIe, DMA, packet buffer, loopback, and management memories expose sticky status bits in their region-specific status registers. Sample those bits with the regular hardware statistics update, preserve the RX and TX packet buffer ECC enable state while clearing RW1C indications, and expose counters grouped by memory region. Each counter records observed indication bits rather than exact error counts because repeated corrections between samples collapse into one sticky bit. On an I350 (8086:1521 revision 1), the ECC enables remained set. All corrected-error status registers remained clear across boot, interface down/up, three FER recovery resets, and bidirectional line-rate traffic. The device has no documented corrected error injector. Therefore, the per-region paths were validated against the register definitions rather than an injected SRAM error. MFC after: 2 weeks Sponsored by: BBOX.io
Diffstat (limited to 'lldb/source/Plugins/Trace/intel-pt/TraceIntelPTMultiCpuDecoder.cpp')
0 files changed, 0 insertions, 0 deletions