On Tue, 21 Mar 2023 11:34:30 +0100 Tomas Mudrunka <tomas.mudrunka@xxxxxxxxx> wrote: > Currently the memtest results were only presented in dmesg. > This adds /proc/meminfo entry which can be easily used by scripts. Looks good to me, thanks. But the changelog still doesn't explain why we should make this change. I grabbed that from your other email and used the below as the changelog: : 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.
