From: Timur Tabi <ttabi@nvidia.com>
To: "airlied@redhat.com" <airlied@redhat.com>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"lyude@redhat.com" <lyude@redhat.com>,
"dakr@redhat.com" <dakr@redhat.com>
Subject: Re: [PATCH] [v2] drm/nouveau: expose GSP-RM logging buffers via debugfs
Date: Thu, 8 Feb 2024 00:08:54 +0000 [thread overview]
Message-ID: <a995c578e39c98acc8a1650883e445bb5b14fd57.camel@nvidia.com> (raw)
In-Reply-To: <20240207194433.3349496-1-ttabi@nvidia.com>
On Wed, 2024-02-07 at 13:44 -0600, Timur Tabi wrote:
> The LOGINIT, LOGINTR, LOGRM, and LOGPMU buffers are circular buffers
> that have printf-like logs from GSP-RM and PMU encoded in them.
>
> LOGINIT, LOGINTR, and LOGRM are allocated by Nouveau and their DMA
> addresses are passed to GSP-RM during initialization. The buffers are
> required for GSP-RM to initialize properly.
I noticed a couple of small errors, so I'll wait for your review and post a
v3.
prev parent reply other threads:[~2024-02-08 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 19:44 [PATCH] [v2] drm/nouveau: expose GSP-RM logging buffers via debugfs Timur Tabi
2024-02-08 0:08 ` Timur Tabi [this message]
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=a995c578e39c98acc8a1650883e445bb5b14fd57.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=lyude@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).