All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@nvidia.com>
To: "dakr@kernel.org" <dakr@kernel.org>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	Ben Skeggs <bskeggs@nvidia.com>,
	"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [PATCH 2/2] [v7] drm/nouveau: expose GSP-RM logging buffers via debugfs
Date: Sat, 3 Aug 2024 03:23:48 +0000	[thread overview]
Message-ID: <d7a748a9c32c2dcb5bbc8d86a62d987d3b6ef7c4.camel@nvidia.com> (raw)
In-Reply-To: <Zq1zDcN2JYTro7VW@cassiopeiae>

On Sat, 2024-08-03 at 02:00 +0200, Danilo Krummrich wrote:
> > +       /* Each GPU has a subdir based on its device name, so find it */
> > +       struct drm_device *drm_dev = dev_get_drvdata(dev);
> 
> In drm-misc-next dev_get_drvdata() returns a struct nouveau_drm.
> Interestingly,
> things do not blow up however.
> 
> Instead, I noticed that your debugfs entries are created in the debugfs
> root,
> instead of "dri/<PCI_ID>/".

Woah.

> I think we shouldn't try to use the DRI debugfs directory anyway to avoid
> DRM
> layer dependencies in nvkm. Let's create our own nouveau one, like you did
> in
> earlier versions of this patch.

So what path should I use?

So what it's supposed to do is create a sort of "shadow" dri/<PCI_ID>/ path
that overlays the existing one.  So when the module deletes the original
dri/<PCI_ID>/, the one I create replaces it automatically.  I think it's a
neat feature.  The path to the debugfs entries stays the same whether or not
they're migrated.  

> Please also make sure to test your patches on a recent drm-misc-next branch.

Will do.

  reply	other threads:[~2024-08-03  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 19:05 [PATCH 1/2] [v2] drm/nouveau: retain device pointer in nvkm_gsp_mem object Timur Tabi
2024-08-02 19:05 ` [PATCH 2/2] [v7] drm/nouveau: expose GSP-RM logging buffers via debugfs Timur Tabi
2024-08-03  0:00   ` Danilo Krummrich
2024-08-03  3:23     ` Timur Tabi [this message]
2024-08-03  9:27       ` Danilo Krummrich

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=d7a748a9c32c2dcb5bbc8d86a62d987d3b6ef7c4.camel@nvidia.com \
    --to=ttabi@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=bskeggs@nvidia.com \
    --cc=dakr@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.