dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Ben Skeggs <bskeggs@nvidia.com>
Cc: Mel Henning <mhenning@darkrefraction.com>,
	Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
	Faith Ekstrand <faith.ekstrand@collabora.com>,
	dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/nouveau: Add DRM_IOCTL_NOUVEAU_GET_ZCULL_INFO
Date: Thu, 20 Mar 2025 21:01:56 +0100	[thread overview]
Message-ID: <Z9x0NLY6HHsvxOFD@pollux> (raw)
In-Reply-To: <abcc6ddc-47d5-4970-8fc1-e82c150fbfd9@nvidia.com>

On Fri, Mar 21, 2025 at 05:57:55AM +1000, Ben Skeggs wrote:
> On 21/3/25 04:18, Danilo Krummrich wrote:
> 
> > Hi Mel,
> > 
> > On Wed, Mar 12, 2025 at 05:36:14PM -0400, Mel Henning wrote:
> 
> > > @@ -72,6 +75,9 @@ struct nvkm_device {
> > >   		bool armed;
> > >   		bool legacy_done;
> > >   	} intr;
> > > +
> > > +	bool has_zcull_info;
> > > +	struct drm_nouveau_get_zcull_info zcull_info;
> > This is bypassing the nvif layer entirely. I think you should store the contents
> > of struct NV2080_CTRL_GR_GET_ZCULL_INFO_PARAMS in struct r535_gr and have an
> > nvif interface to access the data.
> 
> I agree here, though nvkm_gr would be a better choice for a couple of
> reasons, not least that it's possible (and should be reasonably trivial) to
> support this on earlier GPUs - should someone desire to at a later point.

I agree, if the interface is stable enough -- I don't know whether this is prone
to change or not.

  reply	other threads:[~2025-03-20 20:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 21:36 [PATCH 0/2] drm/nouveau: ZCULL support Mel Henning
2025-03-12 21:36 ` [PATCH 1/2] drm/nouveau: Add DRM_IOCTL_NOUVEAU_GET_ZCULL_INFO Mel Henning
2025-03-20 18:18   ` Danilo Krummrich
2025-03-20 18:37     ` Danilo Krummrich
2025-03-20 19:57     ` Ben Skeggs
2025-03-20 20:01       ` Danilo Krummrich [this message]
2025-03-25 23:40         ` M Henning
2025-03-27 12:56           ` Danilo Krummrich
2025-03-27 18:26             ` M Henning
2025-03-28 11:04               ` Danilo Krummrich
2025-03-21 22:06     ` M Henning
2025-03-27 13:51       ` Danilo Krummrich
2025-03-27 18:03         ` M Henning
2025-03-28 11:09           ` Danilo Krummrich
2025-03-12 21:36 ` [PATCH 2/2] drm/nouveau: DRM_NOUVEAU_SET_ZCULL_CTXSW_BUFFER Mel Henning
2025-03-20 18:34   ` Danilo Krummrich
2025-03-21 23:00     ` M Henning
2025-03-27 13:58       ` Danilo Krummrich
2025-03-27 19:01         ` M Henning
2025-03-28 11:48           ` Danilo Krummrich
2025-08-01  2:15             ` M Henning

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=Z9x0NLY6HHsvxOFD@pollux \
    --to=dakr@kernel.org \
    --cc=bskeggs@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=faith.ekstrand@collabora.com \
    --cc=kherbst@redhat.com \
    --cc=lyude@redhat.com \
    --cc=mhenning@darkrefraction.com \
    --cc=nouveau@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).