From: Meijing Zhao <zhaomeijing100@gmail.com>
To: Lorenzo Stoakes <ljs@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Meijing Zhao <zhaomeijing@lixiang.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Wandun Chen <chenwandun@lixiang.com>,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] mm: trace: decode architecture-specific VMA flags
Date: Wed, 2 Sep 2026 14:45:07 +0800 [thread overview]
Message-ID: <cover.1788330432.git.zhaomeijing@lixiang.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.
Changes in v2:
- Rebase onto v7.3-rc1.
- Fix the patch 1 changelog: "bti" and "adi" are descriptive trace
names, but do not match the two-character smaps mnemonics.
- Cc Lorenzo Stoakes.
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-09-02 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 6:45 Meijing Zhao [this message]
2026-09-02 6:45 ` [PATCH v2 1/3] mm: trace: decode arm64 and sparc64 VM_ARCH_1 flags Meijing Zhao
2026-09-02 6:45 ` [PATCH v2 2/3] mm: trace: decode MTE and shadow stack VMA flags Meijing Zhao
2026-09-02 6:45 ` [PATCH v2 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=cover.1788330432.git.zhaomeijing@lixiang.com \
--to=zhaomeijing100@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenwandun@lixiang.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@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