From: Bastien Curutchet via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Fiona Klute <fiona.klute@gmx.de>,
Bastien Curutchet <bastien.curutchet@bootlin.com>
Subject: [Buildroot] [PATCH v4 0/2] package: add rasdaemon support.
Date: Fri, 19 Dec 2025 17:30:14 +0100 [thread overview]
Message-ID: <20251219-rasdaemon-v4-0-2cdc992de787@bootlin.com> (raw)
Hi all,
Rasdaemon is a tool that provides a way to collect all hardware error
events reported by the Linux kernel in a common framework.
My use case is on a PowerPC P2020. I use to it to monitor and react to
the PCIe AER events caught by the SoC's EDAC.
The first patch adds the package. The second one adds a small test for
it in support/testing. Adding fake error injections in the selftest
isn't trivial so it only ensures the daemon does run.
Signed-off-by: Bastien Curutchet <bastien.curutchet@bootlin.com>
---
Changes in v4:
- Add BR2_TOOLCHAIN_HAS_THREADS
- Make the sqlite dependency optional
- Fix Config.in format
- Add Fiona reviewed-by
- Link to v3: https://lore.kernel.org/r/20251201-rasdaemon-v3-0-8ad394bdc372@bootlin.com
Changes in v3:
- PATCH 1: Init script: Run the daemon in foreground and use
--background to leave the PID file creation to start-stop-daemon
- Link to v2: https://lore.kernel.org/r/20251127-rasdaemon-v2-0-c57284751172@bootlin.com
Changes in v2:
- PATCH 1:
Init script: Use a PID file
Config.in: Add comment for the BR2_SHARED_LIBS dependency, fix the AER feature description
rasdaemon.mk: Add License's hash
- PATCH 2:
Add a check to ensure the daemon does run once started by the init
script.
- Link to v1: https://lore.kernel.org/r/20251126-rasdaemon-v1-0-38c590f3e591@bootlin.com
---
Bastien Curutchet (2):
package/rasdaemon: Add rasdaemon package
support/testing: add rasdaemon tests
DEVELOPERS | 4 ++
package/Config.in | 1 +
...aemon-fix-build-when-sqlite-isn-t-enabled.patch | 46 ++++++++++++++++
package/rasdaemon/Config.in | 26 +++++++++
package/rasdaemon/S95rasdaemon | 63 ++++++++++++++++++++++
package/rasdaemon/rasdaemon.hash | 3 ++
package/rasdaemon/rasdaemon.mk | 40 ++++++++++++++
support/testing/tests/package/test_rasdaemon.py | 46 ++++++++++++++++
.../package/test_rasdaemon/linux-debugfs.fragment | 8 +++
9 files changed, 237 insertions(+)
---
base-commit: c8cb1a238de5a803228f12ad32b36cae2acfc778
change-id: 20251125-rasdaemon-1df4904ddfde
Best regards,
--
Bastien Curutchet <bastien.curutchet@bootlin.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-12-19 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 16:30 Bastien Curutchet via buildroot [this message]
2025-12-19 16:30 ` [Buildroot] [PATCH v4 1/2] package/rasdaemon: Add rasdaemon package Bastien Curutchet via buildroot
2025-12-31 9:46 ` Thomas Petazzoni via buildroot
2025-12-19 16:30 ` [Buildroot] [PATCH v4 2/2] support/testing: add rasdaemon tests Bastien Curutchet via buildroot
2025-12-31 9:48 ` Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251219-rasdaemon-v4-0-2cdc992de787@bootlin.com \
--to=buildroot@buildroot.org \
--cc=bastien.curutchet@bootlin.com \
--cc=fiona.klute@gmx.de \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.