From: "Danilo Krummrich" <dakr@kernel.org>
To: "Philipp Stanner" <phasta@mailbox.org>
Cc: phasta@kernel.org, "Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>,
dri-devel@lists.freedesktop.org, kernel-dev@igalia.com,
nouveau@lists.freedesktop.org,
"Alice Ryhl" <aliceryhl@google.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Christian König" <christian.koenig@amd.com>,
"Gary Guo" <gary@garyguo.net>
Subject: Re: [PATCH v3] drm/nouveau: Simplify nouveau_cli_work
Date: Mon, 22 Jun 2026 19:51:03 +0200 [thread overview]
Message-ID: <DJFROOH493EG.1ODJ1NF6VVMPV@kernel.org> (raw)
In-Reply-To: <d3e27b911dd1c0261c2c4d7d65d12d6c1aef58ff.camel@mailbox.org>
On Mon Jun 22, 2026 at 10:57 AM CEST, Philipp Stanner wrote:
> Tvrtko's patch does not address the RCU issues you mention, nor does it
> address any other fence related issue except for adding the comment that
> should have been added back then with the fix in nouveau_cli_work_ready().
I described exactly that, with the goal to discuss a proper solution rather than
arguing about which hack is the better one.
prev parent reply other threads:[~2026-06-22 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 16:54 [PATCH] drm/nouveau: Simplify nouveau_cli_work Tvrtko Ursulin
2026-06-12 17:14 ` Philipp Stanner
2026-06-12 17:18 ` Tvrtko Ursulin
2026-06-12 17:29 ` Tvrtko Ursulin
2026-06-12 17:22 ` [PATCH v2] " Tvrtko Ursulin
2026-06-15 9:26 ` [PATCH v3] " Tvrtko Ursulin
2026-06-15 9:31 ` Philipp Stanner
2026-06-21 15:29 ` Danilo Krummrich
2026-06-21 15:30 ` Danilo Krummrich
2026-06-22 8:57 ` Philipp Stanner
2026-06-22 9:53 ` Tvrtko Ursulin
2026-06-22 12:17 ` Christian König
2026-06-22 12:45 ` Philipp Stanner
2026-06-22 18:20 ` Danilo Krummrich
2026-06-22 17:51 ` 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=DJFROOH493EG.1ODJ1NF6VVMPV@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=kernel-dev@igalia.com \
--cc=nouveau@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=phasta@mailbox.org \
--cc=tvrtko.ursulin@igalia.com \
/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