On 11/19/25 10:59, Xie Yuanbin wrote:
The commit 97f0b13452198290799f ("tracing: add trace event for
memory-failure") introduces the selection of RAS in memory-failure.
This commit is just a tracing feature; in reality, there is no dependency
between memory-failure and RAS. RAS increases the size of the bzImage
image by 8k, which is very valuable for embedded devices.

Move the memory-failure traceing code from ras_event.h to
memory-failure.h and remove the selection of RAS.

v2->v3: https://lore.kernel.org/[email protected]
   - Change define TRACE_SYSTEM from ras to memory_failure
   - Add include/trace/events/memory-failure.h to
     "HWPOISON MEMORY FAILURE HANDLING" section in MAINTAINERS
   - Rebase to latest linux-next source

v1->v2: https://lore.kernel.org/[email protected]
   - Move the memory-failure traceing code from ras_event.h to
     memory-failure.h

Signed-off-by: Xie Yuanbin <[email protected]>
Cc: David Hildenbrand (Red Hat) <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Miaohe Lin <[email protected]>
---
  MAINTAINERS                           |  1 +
  include/ras/ras_event.h               | 87 ------------------------
  include/trace/events/memory-failure.h | 98 +++++++++++++++++++++++++++
  mm/Kconfig                            |  1 -
  mm/memory-failure.c                   |  5 +-
  5 files changed, 103 insertions(+), 89 deletions(-)
  create mode 100644 include/trace/events/memory-failure.h

diff --git a/MAINTAINERS b/MAINTAINERS
index 7310d9ca0370..43d6eb95fb05 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11631,10 +11631,11 @@ R:    Naoya Horiguchi <[email protected]>
  L:    [email protected]
  S:    Maintained
  F:    include/linux/memory-failure.h
  F:    mm/hwpoison-inject.c
  F:    mm/memory-failure.c
+F:     include/trace/events/memory-failure.

These are ordered alphabetically, so it should be further up next to the other include.

With that

Acked-by: David Hildenbrand (Red Hat) <[email protected]>

--
Cheers

David

Reply via email to