From: "Leon Romanovsky" <leon@kernel.org>
To: "Helge Deller" <deller@gmx.de>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Guenter Roeck" <linux@roeck-us.net>
Subject: Re: [PATCH] parisc: Set valid bit in high byte of 64‑bit physical address
Date: Thu, 18 Dec 2025 23:28:36 +0200 [thread overview]
Message-ID: <91700541-3c17-4c2f-aa6b-b4e1a36749f9@app.fastmail.com> (raw)
In-Reply-To: <23342800-92be-4288-a9cd-e9e436a2ef87@gmx.de>
On Thu, Dec 18, 2025, at 20:27, Helge Deller wrote:
> Hi Leon,
>
> On 12/18/25 13:08, Leon Romanovsky wrote:
>> On 32‑bit systems, phys_addr_t is defined as u32. However, parisc
>> expects physical addresses to be 64‑bit values so it can store a
>> validity bit in the upper byte.
>> ...
>> Also remove the now‑obsolete macro.
>
> Your patch is OK, but could you please keep the lpa() macro?
> It's unrelated to your patch, and sometimes we need the lpa()
> e.g. when adding debug code, so I'd prefer to keep it.
The parch was already accepted and if Marek agrees, he can easily revert the deleted hunk and rebase my parch.
However from upstream perspective, we don't keep code which is not used and if this macro would be function, we would get compilation warning for that.
Isn't lpa(x/) equal to virt_to_phys(x)?
Thanks
>
> Thanks,
> Helge
>
> ...
>> diff --git a/arch/parisc/include/asm/special_insns.h b/arch/parisc/include/asm/special_insns.h
>> index 1013eeba31e5..fbccd76180b6 100644
>> --- a/arch/parisc/include/asm/special_insns.h
>> +++ b/arch/parisc/include/asm/special_insns.h
>> @@ -2,21 +2,6 @@
>> #ifndef __PARISC_SPECIAL_INSNS_H
>> #define __PARISC_SPECIAL_INSNS_H
>>
>> -#define lpa(va) ({ \
>> - unsigned long pa; \
>> - __asm__ __volatile__( \
>> - "copy %%r0,%0\n" \
>> - "8:\tlpa %%r0(%1),%0\n" \
>> - "9:\n" \
>> - ASM_EXCEPTIONTABLE_ENTRY(8b, 9b, \
>> - "or %%r0,%%r0,%%r0") \
>> - : "=&r" (pa) \
>> - : "r" (va) \
>> - : "memory" \
>> - ); \
>> - pa; \
>> -})
next prev parent reply other threads:[~2025-12-18 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:08 [PATCH] parisc: Set valid bit in high byte of 64‑bit physical address Leon Romanovsky
2025-12-18 16:22 ` Guenter Roeck
2025-12-18 17:14 ` Marek Szyprowski
2025-12-18 18:27 ` Helge Deller
2025-12-18 21:28 ` Leon Romanovsky [this message]
2025-12-19 8:35 ` Marek Szyprowski
2025-12-19 12:38 ` James Bottomley
2025-12-19 12:48 ` Marek Szyprowski
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=91700541-3c17-4c2f-aa6b-b4e1a36749f9@app.fastmail.com \
--to=leon@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=m.szyprowski@samsung.com \
/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