From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
linux-mm@kvack.org, usama.arif@linux.dev, hughd@google.com,
ryan.roberts@arm.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] mm: Standardize printing for pgtable entries
Date: Mon, 27 Jul 2026 18:20:39 +0530 [thread overview]
Message-ID: <bccce409-e105-4a7a-b962-35905dc1ff38@arm.com> (raw)
In-Reply-To: <alUM69tP-Zayp1Jk@ashevche-desk.local>
On 13/07/26 9:36 PM, Andy Shevchenko wrote:
> On Mon, Jul 13, 2026 at 01:34:17PM +0100, Matthew Wilcox wrote:
>> On Mon, Jul 13, 2026 at 02:36:50PM +0300, Andy Shevchenko wrote:
>>> FWIW, we have hex_dump_to_buffer() for that already.
>>
>> ... which doesn't eliminate the problem of allocating buffers in the
>> caller.
>
> Right, for this we need to integrate hex_dump_to_buffer() into %ph.
Would not that create more complexity which might not really
be required here for simple pgtable entry print solution that
would probably have very limited number of callers anyway. Is
not that reason - we did not go for the original printk format
proposed earlier.
https://lore.kernel.org/all/20260610043545.3725735-1-anshuman.khandual@arm.com/
IMHO this should be left unchanged. Later if there are more
users for such prints, those printk formats should again be
evaluated.
- Anshuman
prev parent reply other threads:[~2026-07-27 12:50 UTC|newest]
Thread overview: 25+ 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)
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
2026-07-27 12:50 ` Anshuman Khandual [this message]
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=bccce409-e105-4a7a-b962-35905dc1ff38@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.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