From: Meijing Zhao <zhaomeijing100@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Meijing Zhao <zhaomeijing@lixiang.com>
Subject: [PATCH RESEND 0/3] mm: trace: decode architecture-specific VMA flags
Date: Thu, 23 Jul 2026 17:29:02 +0800 [thread overview]
Message-ID: <20260723092905.761037-1-zhaomeijing100@gmail.com> (raw)
From: Meijing Zhao <zhaomeijing@lixiang.com>
show_vma_flags(), which is used by VMA tracepoints and %pGv, names
generic VM_* bits but does not fully decode architecture-specific flag
positions. As a result, trace output and VMA dumps can show a generic
"arch_1" name or a raw hexadecimal value instead of the meaning assigned
by the target architecture.
This series adds symbolic names for the arm64 and sparc64 meanings of
VM_ARCH_1, arm64 MTE flags, user shadow stack flags, and protection-key
encoding bits under their corresponding configuration guards.
The original submission was rewritten by the mail gateway as a
multipart HTML message and had a disclaimer appended, causing the vger
mailing lists to reject it. This resend uses a mail transport that
preserves plain-text messages. There are no code changes.
Meijing Zhao (3):
mm: trace: decode arm64 and sparc64 VM_ARCH_1 flags
mm: trace: decode MTE and shadow stack VMA flags
mm: trace: name protection key encoding bits
include/trace/events/mmflags.h | 43 ++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
--
2.25.1
next reply other threads:[~2026-07-23 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:29 Meijing Zhao [this message]
2026-07-23 9:29 ` [PATCH RESEND 1/3] mm: trace: decode arm64 and sparc64 VM_ARCH_1 flags Meijing Zhao
2026-07-23 9:29 ` [PATCH RESEND 2/3] mm: trace: decode MTE and shadow stack VMA flags Meijing Zhao
2026-07-23 9:29 ` [PATCH RESEND 3/3] mm: trace: name protection key encoding bits Meijing Zhao
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=20260723092905.761037-1-zhaomeijing100@gmail.com \
--to=zhaomeijing100@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zhaomeijing@lixiang.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