diff options
| author | Tomas Mudrunka <tomas.mudrunka@gmail.com> | 2023-03-21 13:34:30 +0300 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-04-06 05:42:55 +0300 |
| commit | bd23024b9774e681cbe6cc3afcb24244dfcb2390 (patch) | |
| tree | 660d52ca5ef5b776a2299b5a189add72d34c39c9 /mm/memory.c | |
| parent | c9bb52738b39fabc8b6b9446f0d194eedb3e5a10 (diff) | |
| download | linux-bd23024b9774e681cbe6cc3afcb24244dfcb2390.tar.xz | |
mm/memtest: add results of early memtest to /proc/meminfo
Currently the memtest results were only presented in dmesg.
When running a large fleet of devices without ECC RAM it's currently not
easy to do bulk monitoring for memory corruption. You have to parse
dmesg, but that's a ring buffer so the error might disappear after some
time. In general I do not consider dmesg to be a great API to query RAM
status.
In several companies I've seen such errors remain undetected and cause
issues for way too long. So I think it makes sense to provide a
monitoring API, so that we can safely detect and act upon them.
This adds /proc/meminfo entry which can be easily used by scripts.
Link: https://lkml.kernel.org/r/20230321103430.7130-1-tomas.mudrunka@gmail.com
Signed-off-by: Tomas Mudrunka <tomas.mudrunka@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Mike Rapoport (IBM) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions