From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
Hugh Dickins <hughd@google.com>
Cc: linux-mm@kvack.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Lorenzo Stoakes <ljs@kernel.org>
Subject: Re: [RFC V2 3/3] mm: Replace pgtable entry prints with new format
Date: Thu, 2 Jul 2026 11:36:57 +0200 [thread overview]
Message-ID: <4467a8ad-a298-47da-99e7-b97793d9348f@kernel.org> (raw)
In-Reply-To: <e4ec99fc-dfb1-4205-a193-f694e9f6a13b@arm.com>
On 7/2/26 11:04, Anshuman Khandual wrote:
>
> On 02/07/26 1:02 PM, David Hildenbrand (Arm) wrote:
>> On 7/2/26 06:29, Anshuman Khandual wrote:
>>>
>>>
>>>
>>> Could this be made sizeof(u128) instead ? But overall this
>>> approach looks good.
>>
>> The would be cleaner. We might have to protect this case by something like
>>
>> #defined(__SIZEOF_INT128__)
>> case sizeof(u128):
>> ...
>> break;
>> #endif
>> default:
>
> Right - realized that just a bit later :) Not all
> platforms and corresponding tool chains might not
> support u128.
If we actually go for u128, could that make printing easier?
Like, cast the buffer to an u128 and then simply shift the u64 values into place?
I wasn't quite sure if what I do in my patch is actually correct.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-02 9:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 4:35 [RFC V2 0/3] lib/vsprintf: Add support for pgtable entries Anshuman Khandual
2026-06-10 4:35 ` [RFC V2 1/3] " Anshuman Khandual
2026-06-10 11:13 ` Usama Arif
2026-06-11 5:15 ` Anshuman Khandual
2026-06-11 7:17 ` Andy Shevchenko
2026-06-11 9:50 ` Anshuman Khandual
2026-06-11 18:59 ` Andy Shevchenko
2026-06-10 4:35 ` [RFC V2 2/3] kunit: printf: Add test " Anshuman Khandual
2026-06-10 4:35 ` [RFC V2 3/3] mm: Replace pgtable entry prints with new format Anshuman Khandual
2026-06-11 11:32 ` David Hildenbrand (Arm)
2026-06-12 11:08 ` David Hildenbrand (Arm)
2026-06-12 21:26 ` Hugh Dickins
2026-06-15 16:01 ` David Hildenbrand (Arm)
2026-06-16 6:19 ` Hugh Dickins
2026-06-30 13:36 ` David Hildenbrand (Arm)
2026-07-01 9:00 ` Andy Shevchenko
2026-07-02 4:29 ` Anshuman Khandual
2026-07-02 7:32 ` David Hildenbrand (Arm)
2026-07-02 9:04 ` Anshuman Khandual
2026-07-02 9:20 ` Andy Shevchenko
2026-07-02 9:36 ` David Hildenbrand (Arm) [this message]
2026-06-11 19:15 ` [RFC V2 0/3] lib/vsprintf: Add support for pgtable entries Matthew Wilcox
2026-06-11 19:33 ` Andy Shevchenko
2026-06-11 19:37 ` Matthew Wilcox
2026-06-12 11:14 ` 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=4467a8ad-a298-47da-99e7-b97793d9348f@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=corbet@lwn.net \
--cc=hughd@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ljs@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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