From: Danilo Krummrich <dakr@kernel.org>
To: Zhi Wang <zhiw@nvidia.com>
Cc: nouveau@lists.freedesktop.org, airlied@gmail.com,
daniel@ffwll.ch, lyude@redhat.com, bskeggs@nvidia.com,
acurrid@nvidia.com, cjia@nvidia.com, smitra@nvidia.com,
ankita@nvidia.com, aniketa@nvidia.com, kwankhede@nvidia.com,
targupta@nvidia.com, zhiwang@kernel.org
Subject: Re: [PATCH v3 0/2] NVKM GSP RPC message handling policy
Date: Sun, 9 Mar 2025 14:00:29 +0100 [thread overview]
Message-ID: <Z82Q7edxvy3_H4DT@cassiopeiae> (raw)
In-Reply-To: <20250227013554.8269-1-zhiw@nvidia.com>
On Thu, Feb 27, 2025 at 01:35:52AM +0000, Zhi Wang wrote:
> Hi folks:
>
> Here are the v3 version of NVKM GSP RPC message handling policy which
> solves the issue reported by Ben. More details can be found in v1 [1].
>
> v3:
>
> - Fix a hidden use-after-free caught by KFENCE in PATCH 1,
> r535_gsp_rpc_send(). (Ben)
>
> Zhi Wang (2):
> drm/nouveau/nvkm: factor out current GSP RPC command policies
> drm/nouveau/nvkm: introduce new GSP reply policy
> NVKM_GSP_RPC_REPLY_POLL
>
> Documentation/gpu/nouveau.rst | 3 +
> .../gpu/drm/nouveau/include/nvkm/subdev/gsp.h | 38 +++++++--
> .../gpu/drm/nouveau/nvkm/subdev/bar/r535.c | 2 +-
> .../gpu/drm/nouveau/nvkm/subdev/gsp/r535.c | 78 ++++++++++---------
> .../drm/nouveau/nvkm/subdev/instmem/r535.c | 2 +-
> 5 files changed, 79 insertions(+), 44 deletions(-)
Applied to drm-misc-next, thanks!
prev parent reply other threads:[~2025-03-09 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 1:35 [PATCH v3 0/2] NVKM GSP RPC message handling policy Zhi Wang
2025-02-27 1:35 ` [PATCH v3 1/2] drm/nouveau/nvkm: factor out current GSP RPC command policies Zhi Wang
2025-02-27 1:46 ` Timur Tabi
2025-03-14 1:39 ` Alexandre Courbot
2025-03-14 8:09 ` Zhi Wang
2025-02-27 1:35 ` [PATCH v3 2/2] drm/nouveau/nvkm: introduce new GSP reply policy NVKM_GSP_RPC_REPLY_POLL Zhi Wang
2025-03-09 13:00 ` Danilo Krummrich [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=Z82Q7edxvy3_H4DT@cassiopeiae \
--to=dakr@kernel.org \
--cc=acurrid@nvidia.com \
--cc=airlied@gmail.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=bskeggs@nvidia.com \
--cc=cjia@nvidia.com \
--cc=daniel@ffwll.ch \
--cc=kwankhede@nvidia.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=smitra@nvidia.com \
--cc=targupta@nvidia.com \
--cc=zhiw@nvidia.com \
--cc=zhiwang@kernel.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.