mm/memtest: add results of early memtest to /proc/meminfo
authorTomas Mudrunka <tomas.mudrunka@gmail.com>
Tue, 21 Mar 2023 10:34:30 +0000 (11:34 +0100)
committerAndrew Morton <akpm@linux-foundation.org>
Thu, 6 Apr 2023 02:42:55 +0000 (19:42 -0700)
commitbd23024b9774e681cbe6cc3afcb24244dfcb2390
tree660d52ca5ef5b776a2299b5a189add72d34c39c9
parentc9bb52738b39fabc8b6b9446f0d194eedb3e5a10
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>
Documentation/filesystems/proc.rst
fs/proc/meminfo.c
include/linux/memblock.h
mm/memtest.c