Re: [RFC PATCH v3 0/3] trace: stack trace deduplication for ftrace ring buffer

[Steven Rostedt]

Please DO NOT SEND new versions of a patch or patch series as a reply to
the old one. It makes it extremely difficult for maintainers to manage the
replies and patches.

A new version should ALWAYS start a new email thread!

On Tue, 26 May 2026 19:52:42 +0800
Li Pengfei <ljdlns1987@xxxxxxxxx> wrote:

> From: Pengfei Li <lipengfei28@xxxxxxxxxx>
> 
> Hi Masami, Steven, all,
> 
> This is v3 of the ftrace stackmap series. It addresses the Sashiko
> review on v2 [1] that Masami pointed out.
> 
> [1] https://sashiko.dev/#/patchset/20260522104017.1668638-1-lipengfei28%40xiaomi.com
> 
> The series adds stack trace deduplication to ftrace. When the
> stacktrace option is enabled, the ring buffer stores a 4-byte
> stack_id instead of a full kernel stack trace, while the full
> stacks are exported via tracefs.
> 
> Rebased onto v7.1-rc5 (e8c2f9fdadee) before sending.
> 
> Changes since v2
> ================

Then you can use lore to add a link to the old version via the Message-ID
of the old version. You can have the above as:

 Changes since v2: https://lore.kernel.org/all/20260522104017.1668638-1-lipengfei28@xxxxxxxxxx/

-- Steve