[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <670878b5-23fc-4b11-b585-9ddd43576963@arm.com>
Date: Fri, 20 Jun 2025 12:00:55 +0530
From: Anshuman Khandual <anshuman.khandual@....com>
To: David Hildenbrand <david@...hat.com>, linux-mm@...ck.org
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Petr Mladek
<pmladek@...e.com>, Steven Rostedt <rostedt@...dmis.org>,
Jonathan Corbet <corbet@....net>, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [RFC 1/2] lib/vsprintf: Add support for pte_t
On 18/06/25 2:13 PM, David Hildenbrand wrote:
> On 18.06.25 10:33, Anshuman Khandual wrote:
>>
>>
>> On 18/06/25 1:49 PM, David Hildenbrand wrote:
>>>> + case 'p':
>>>> + if (fmt[1] == 't' && fmt[2] == 'e') {
>>>> + pte_t *pte = (pte_t *)ptr;
>>>> +
>>>> + spec.field_width = 10;
>>>> + spec.precision = 8;
>>>> + spec.base = 16;
>>>> + spec.flags = SPECIAL | SMALL | ZEROPAD;
>>>> + if (sizeof(pte_t) == sizeof(u64)) {
>>>> + u64 val = pte_val(*pte);
>>>> +
>>>> + return number(buf, end, val, spec);
>>>> + }
>>>> + WARN_ONCE(1, "Non standard pte_t\n");
>>>
>>> What about 32bit with 32bit pte_t?
>>
>> Ahh, missed that. Just wondering which all platforms might
>> care about the 32 bit pte representation.
>
> I think e.g., 32bit arm has 32bit ptes?
>
> arch/arm/include/asm/pgtable-2level-types.h
>
> typedef u32 pteval_t;
> ...
> typedef struct { pteval_t pte; } pte_t;
Right, missed that. I will accommodate 32 bit representations.
Powered by blists - more mailing lists