From: Andrew Morton <akpm@linux-foundation.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, andriy.shevchenko@linux.intel.com,
usama.arif@linux.dev, hughd@google.com, willy@infradead.org,
ryan.roberts@arm.com,
"David Hildenbrand (Arm)" <david@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] mm: Standardize printing for pgtable entries
Date: Thu, 9 Jul 2026 20:32:21 -0700 [thread overview]
Message-ID: <20260709203221.573de46038f027c2ccad641e@linux-foundation.org> (raw)
In-Reply-To: <25857f58-9ef1-49e0-99f7-366d91028c02@arm.com>
On Fri, 10 Jul 2026 08:40:25 +0530 Anshuman Khandual <anshuman.khandual@arm.com> wrote:
>
>
> On 10/07/26 5:38 AM, Andrew Morton wrote:
> > On Thu, 9 Jul 2026 10:13:34 +0530 Anshuman Khandual <anshuman.khandual@arm.com> wrote:
> >
> >> From: "David Hildenbrand (Arm)" <david@kernel.org>
> >>
> >> Bad page map reporting currently stores page table entry values in an
> >> unsigned long long and prints them with fixed 64-bit-oriented format
> >> strings. This is inconsistent across call sites and does not work well for
> >> architectures where page table entry values are not naturally represented
> >> as 64-bit values, such as 32-bit or 128-bit entries.
> >
> > Well grumble. It's a lot of fuss for something which nobody is hurting
> > from. Or are they? What's the actual utility here?
>
> Current page table entries print does not work here for
> 128 bits format (arm64 D128) because neither 'unsigned
> long long' can hold 128 bits nor printing extracts u64
> from the 128 bit entries while printing with "%llx".
>
> Proposed a separate printk format %pp[te|md|ud|p4d|gd]
>
> https://lore.kernel.org/all/20260610043545.3725735-1-anshuman.khandual@arm.com/
>
> But there after it was decided to rather have a local
> solution in mm/memory.c instead of adding a new print
> format.
OK, thanks. Let's please spell such things out in the changelogging.
Explaining how a change helps our users (ie, improves Linux) is super
important!
> >> if (!pgd_present(*pgdp) || pgd_leaf(*pgdp)) {
> >> - pr_alert("pgd:%08llx\n", pgdv);
> >> + pr_alert("pgd:%s\n", pgd_str);
> >
> > can this do
> > pr_alert("pgd:%s\n", ptval_to_str(pgd_str, pgd_val(*pgdp)));
> >
> > and eliminate a few locals?
>
> But that would not eliminate any local variable.
>
> The helper ptval_to_str() does not return but instead
> fills up the provided buffer which later gets printed.
Well yes. Changing it to return `buf' was kinda implicit!
next prev parent reply other threads:[~2026-07-10 3:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:43 [PATCH V3] mm: Standardize printing for pgtable entries Anshuman Khandual
2026-07-09 7:40 ` Andy Shevchenko
2026-07-09 9:12 ` David Hildenbrand (Arm)
2026-07-09 10:09 ` Andy Shevchenko
2026-07-09 10:19 ` David Hildenbrand (Arm)
2026-07-09 9:15 ` Petr Mladek
2026-07-09 10:11 ` Andy Shevchenko
2026-07-09 10:13 ` Andy Shevchenko
2026-07-09 10:24 ` David Hildenbrand (Arm)
2026-07-09 10:43 ` Andy Shevchenko
2026-07-09 11:12 ` Anshuman Khandual
2026-07-09 11:54 ` Andy Shevchenko
2026-07-10 0:08 ` Andrew Morton
2026-07-10 3:10 ` Anshuman Khandual
2026-07-10 3:32 ` Andrew Morton [this message]
2026-07-10 8:16 ` David Hildenbrand (Arm)
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=20260709203221.573de46038f027c2ccad641e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=willy@infradead.org \
/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