From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Xie Yuanbin <xieyuanbin1@huawei.com>,
tony.luck@intel.com, bp@alien8.de, linmiaohe@huawei.com,
nao.horiguchi@gmail.com, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org,
will@kernel.org, liaohua4@huawei.com, lilinjie8@huawei.com
Subject: Re: [PATCH v3] mm/memory-failure: remove the selection of RAS
Date: Thu, 20 Nov 2025 14:59:54 +0100 [thread overview]
Message-ID: <fc7bae22-0705-475a-be89-8bb3ca12384d@kernel.org> (raw)
In-Reply-To: <20251119095943.67125-1-xieyuanbin1@huawei.com>
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/20251104072306.100738-3-xieyuanbin1@huawei.com
> - 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/20251103033536.52234-2-xieyuanbin1@huawei.com
> - Move the memory-failure traceing code from ras_event.h to
> memory-failure.h
>
> Signed-off-by: Xie Yuanbin <xieyuanbin1@huawei.com>
> Cc: David Hildenbrand (Red Hat) <david@kernel.org>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Miaohe Lin <linmiaohe@huawei.com>
> ---
> 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 <nao.horiguchi@gmail.com>
> L: linux-mm@kvack.org
> 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) <david@kernel.org>
--
Cheers
David
next prev parent reply other threads:[~2025-11-20 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:59 Xie Yuanbin
2025-11-20 13:59 ` David Hildenbrand (Red Hat) [this message]
2025-11-20 15:56 ` Andrew Morton
2025-11-21 7:39 ` Miaohe Lin
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=fc7bae22-0705-475a-be89-8bb3ca12384d@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=liaohua4@huawei.com \
--cc=lilinjie8@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=xieyuanbin1@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox