From: James Jones <jajones@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Lyude Paul <lyude@redhat.com>,
Faith Ekstrand <faith.ekstrand@collabora.com>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Joel Fernandes <joelagnelf@nvidia.com>
Subject: Re: [PATCH 1/3] drm: define NVIDIA DRM format modifiers for GB20x
Date: Tue, 14 Oct 2025 17:10:21 -0700 [thread overview]
Message-ID: <739f05b1-a72f-40df-bcb9-28f33aced5ff@nvidia.com> (raw)
In-Reply-To: <1cbcceed-6e95-4f20-8666-1c8f40154e3b@kernel.org>
On 9/2/25 06:41, Danilo Krummrich wrote:
> On 8/12/25 12:00 AM, James Jones wrote:
>> The layout of bits within the individual tiles
>> (referred to as sectors in the
>> DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D() macro)
>> changed for 8 and 16-bit surfaces starting in
>> Blackwell 2 GPUs (With the exception of GB10).
>> To denote the difference, extend the sector field
>> in the parametric format modifier definition used
>> to generate modifier values for NVIDIA hardware.
>>
>> Without this change, it would be impossible to
>> differentiate the two layouts based on modifiers,
>> and as a result software could attempt to share
>> surfaces directly between pre-GB20x and GB20x
>> cards, resulting in corruption when the surface
>> was accessed on one of the GPUs after being
>> populated with content by the other.
>>
>> Of note: This change causes the
>> DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D() macro to
>> evaluate its "s" parameter twice, with the side
>> effects that entails. I surveyed all usage of the
>> modifier in the kernel and Mesa code, and that
>> does not appear to be problematic in any current
>> usage, but I thought it was worth calling out.
>>
>> Signed-off-by: James Jones <jajones@nvidia.com>
>
> Having a second look on this, isn't this (and patch 3) a fix as well?
Sorry, it was just pointed out that I missed this email. Apologies.
I suppose they could be considered a fix for 6cc6e08d4542
("drm/nouveau/kms: add support for GB20x"). Would you like me to send
out a rebased v2 with a Fixes tag?
Thanks,
-James
next prev parent reply other threads:[~2025-10-15 0:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 22:00 [PATCH 0/3] drm/nouveau: Advertise correct modifiers on GB20x James Jones
2025-08-11 22:00 ` [PATCH 1/3] drm: define NVIDIA DRM format modifiers for GB20x James Jones
2025-08-22 16:16 ` Faith Ekstrand
2025-09-02 13:41 ` Danilo Krummrich
2025-10-15 0:10 ` James Jones [this message]
2025-08-11 22:00 ` [PATCH 2/3] drm/nouveau/disp: Always accept linear modifier James Jones
2025-08-22 16:17 ` Faith Ekstrand
2025-08-22 20:55 ` Danilo Krummrich
2025-08-22 21:11 ` James Jones
2025-08-22 21:14 ` Danilo Krummrich
2025-08-22 23:14 ` Danilo Krummrich
2025-08-11 22:00 ` [PATCH 3/3] drm/nouveau: Advertise correct modifiers on GB20x James Jones
[not found] ` <CAOFGe97AN_yo7Mg4Z7s=qOFzSGzzs6CLEAhByf-ks2GthFj0aw@mail.gmail.com>
2025-08-22 17:03 ` James Jones
2025-08-22 17:10 ` Faith Ekstrand
2025-08-22 20:44 ` [PATCH 0/3] " Faith Ekstrand
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=739f05b1-a72f-40df-bcb9-28f33aced5ff@nvidia.com \
--to=jajones@nvidia.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®