From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: "vladazaharova2018@gmail.com" <vladazaharova2018@gmail.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"gary@garyguo.net" <gary@garyguo.net>,
"nova-gpu@lists.linux.dev" <nova-gpu@lists.linux.dev>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dakr@kernel.org" <dakr@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"aliceryhl@google.com" <aliceryhl@google.com>
Subject: Re: [PATCH v6 0/3] gpu: nova-core: retain the GSP-RM log buffers
Date: Sat, 07 Nov 2026 08:15:26 +0900 [thread overview]
Message-ID: <DMOIDO8EG1W4.W5NWTTZNDB8V@nvidia.com> (raw)
In-Reply-To: <b2ff5c437c41ba4f8c1a8f354d24d7e68517fbf3.camel@nvidia.com>
On Sat Nov 7, 2026 at 5:51 AM JST, Timur Tabi wrote:
> On Wed, 2026-10-14 at 22:45 +0700, Vladislav Zaharov wrote:
>
>> Changes since v5:
>> - keep the "put" pointer read before the barrier in the copy, rather
>> than the one the copy reads again, which is not ordered against the
>> rest of the data (reported by the Sashiko review bot)
>> - rebase onto current drm-rust-next
>
> Can you rebase this onto https://github.com/Gnurou/linux/tree/r000_rebase_all
>
> This tree is the future of rust-drm-next, and there have been some significant changes to
> debugfs that result in a lot of merge conflicts.
This tree is also a moving target; let's not ask contributors to use
obscure bases that are weeks from reconciling with drm-rust-next.
The current v5 applies (almost) cleanly on today's drm-rust-next, so it
is fair game to review and merge if deemed ready. We can rebase our r000
code on top of it should it lands first.
prev parent reply other threads:[~2026-11-06 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 15:45 Vladislav Zaharov
2026-10-14 15:45 ` [PATCH v6 1/3] gpu: nova-core: move the debugfs root into the module data Vladislav Zaharov
2026-10-14 15:45 ` [PATCH v6 2/3] gpu: nova-core: gsp: retain the GSP-RM log buffers after unbind Vladislav Zaharov
2026-10-14 15:45 ` [PATCH v6 3/3] Documentation: nova: remove completed GSP log buffer task Vladislav Zaharov
2026-11-06 20:51 ` [PATCH v6 0/3] gpu: nova-core: retain the GSP-RM log buffers Timur Tabi
2026-11-06 22:52 ` Danilo Krummrich
2026-11-06 23:15 ` John Hubbard
2026-11-06 23:08 ` Alexandre Courbot
2026-11-06 23:15 ` Alexandre Courbot [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=DMOIDO8EG1W4.W5NWTTZNDB8V@nvidia.com \
--to=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ttabi@nvidia.com \
--cc=vladazaharova2018@gmail.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
all inboxes | Powered by JetHome®