From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] mm: Standardize printing for pgtable entries
Date: Fri, 10 Jul 2026 10:16:12 +0200 [thread overview]
Message-ID: <22bae03a-1a7e-41f4-8012-a511c173400d@kernel.org> (raw)
In-Reply-To: <20260709170816.4e876a16eef9a93f41bb1940@linux-foundation.org>
On 7/10/26 02:08, 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?
Hugh seems to rely on this information heavily when debugging
https://lore.kernel.org/r/3afa822d-3cc9-1068-9a10-94a5f2e4d29a@google.com
--
Cheers,
David
next prev parent reply other threads:[~2026-07-10 8:16 UTC|newest]
Thread overview: 24+ 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
2026-07-10 8:16 ` David Hildenbrand (Arm) [this message]
2026-07-11 4:58 ` Matthew Wilcox
2026-07-13 2:37 ` Anshuman Khandual
2026-07-13 9:30 ` David Hildenbrand (Arm)
2026-07-13 11:36 ` Andy Shevchenko
2026-07-13 12:31 ` David Hildenbrand (Arm)
2026-07-13 12:34 ` Matthew Wilcox
2026-07-13 12:37 ` David Hildenbrand (Arm)
2026-07-13 16:06 ` Andy Shevchenko
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=22bae03a-1a7e-41f4-8012-a511c173400d@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.