Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-mm@kvack.org
Cc: andriy.shevchenko@linux.intel.com, usama.arif@linux.dev,
	hughd@google.com, willy@infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] mm: Standardize printing for pgtable entries
Date: Wed, 8 Jul 2026 14:58:51 +0200	[thread overview]
Message-ID: <1e6be746-44b5-485c-8adb-4a21b7a3d03d@kernel.org> (raw)
In-Reply-To: <724a080a-bd4b-4fab-a890-c6a97ebff77f@arm.com>

On 7/8/26 14:43, Ryan Roberts wrote:
> On 08/07/2026 12:27, David Hildenbrand (Arm) wrote:
>> On 7/8/26 13:22, Ryan Roberts wrote:
>>>
>>> Not sure if it's worth doing something like this?:
>>>
>>> #define PTVAL_STR_MAX						\
>>> 	(MAX(MAX(MAX(MAX(sizeof(pteval_t), sizeof(pmdval_t)), 	\
>>> 	    	     sizeof(pudval_t)), 			\
>>> 		 sizeof(p4dval_t)), 				\
>>>     	     sizeof(pgdval_t)) + 1)
>>>
>>> Would probably save stack space for 32bit arches?
>>
>> Do we really care about that? This is about a corner cases error reporting right
>> now.
> 
> Fair enough, it just seemed like an obvious and simple (very minor) improvement.
> 
>>
>>>
>>>
>>> I think arm64 code also does pte printing, which you also need to fix up for
>>> D128 support. Perhaps this could be moved to a header for reuse?
>>
>> We could do that as a second step, right?
> 
> Sure, but why churn it twice? Anyway, no strong opinion, you're the boss :)

I'd say, if we're going to reuse this code for the arm64 pieces as well, we'd
best send it along the arm64 pieces, and figure out where to place it for
arm64's use right away.

If we'll defer the arm64 changes, I'd also defer deciding where we'd be moving
it to.

-- 
Cheers,

David


  reply	other threads:[~2026-07-08 12:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  3:28 [PATCH V2] mm: Standardize printing for pgtable entries Anshuman Khandual
2026-07-08  8:01 ` David Hildenbrand (Arm)
2026-07-08  8:43   ` Anshuman Khandual
2026-07-08  8:52     ` David Hildenbrand (Arm)
2026-07-08 11:17 ` Andy Shevchenko
2026-07-09  3:42   ` Anshuman Khandual
2026-07-08 11:22 ` Ryan Roberts
2026-07-08 11:27   ` David Hildenbrand (Arm)
2026-07-08 12:43     ` Ryan Roberts
2026-07-08 12:58       ` David Hildenbrand (Arm) [this message]
2026-07-09  3:54         ` Anshuman Khandual

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=1e6be746-44b5-485c-8adb-4a21b7a3d03d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox