From: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
To: "Kuehling, Felix" <felix.kuehling@amd.com>,
Christian König <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/ttm: Support 52-bit PAs in ttm_place
Date: Wed, 13 May 2026 20:20:41 +0530 [thread overview]
Message-ID: <7ce2627c-4a64-4cc2-b464-64d7bbdbbf1d@amd.com> (raw)
In-Reply-To: <6dc1e113-c06e-466d-9db2-4e2a2b34ff83@amd.com>
I modified the commit message and pushed into drm-misc-next.
Regards,
Arun.
On 5/13/2026 7:57 PM, Kuehling, Felix wrote:
> On 2026-05-13 09:19, Christian König wrote:
>> On 5/13/26 16:12, Felix Kuehling wrote:
>>> fpfn and lpfn in struct ttm_place are 32-bit page numbers. With 4KB
>>> page
>>> size this can support up to 44-bit physical addressing. Grow these to
>>> unsigned long to support larger physical addresses.
>
> I forgot to update the commit message. It still says unsigned long.
> @Arun, can you update that before you push it to drm-misc-next?
>
> Thanks,
> Felix
>
>
>>>
>>> Signed-off-by: Felix Kuehling <felix.kuehling@amd.com>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>
>> @Arun can you pick that one up and push it to drm-misc-next?
>>
>> Thanks,
>> Christian.
>>
>>> ---
>>> include/drm/ttm/ttm_placement.h | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/include/drm/ttm/ttm_placement.h
>>> b/include/drm/ttm/ttm_placement.h
>>> index b510a4812609..ab2639e42c54 100644
>>> --- a/include/drm/ttm/ttm_placement.h
>>> +++ b/include/drm/ttm/ttm_placement.h
>>> @@ -81,8 +81,8 @@
>>> * Structure indicating a possible place to put an object.
>>> */
>>> struct ttm_place {
>>> - unsigned fpfn;
>>> - unsigned lpfn;
>>> + uint64_t fpfn;
>>> + uint64_t lpfn;
>>> uint32_t mem_type;
>>> uint32_t flags;
>>> };
next prev parent reply other threads:[~2026-05-13 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:12 [PATCH v2] drm/ttm: Support 52-bit PAs in ttm_place Felix Kuehling
2026-05-13 14:19 ` Christian König
2026-05-13 14:27 ` Kuehling, Felix
2026-05-13 14:50 ` Arunpravin Paneer Selvam [this message]
2026-05-13 14:50 ` Tvrtko Ursulin
2026-05-13 15:32 ` Christian König
2026-05-16 1:53 ` Claude review: " Claude Code Review Bot
2026-05-16 1:53 ` Claude Code Review Bot
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=7ce2627c-4a64-4cc2-b464-64d7bbdbbf1d@amd.com \
--to=arunpravin.paneerselvam@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.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