From: Alistair Popple <apopple@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: "SeungJong Ha" <engineer.jjhama@gmail.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Nicolás Antinori" <nico.antinori.7@gmail.com>,
"David Airlie" <airlied@gmail.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Simona Vetter" <simona@ffwll.ch>, "Gary Guo" <gary@garyguo.net>,
"Onur Özkan" <work@onurozkan.dev>,
"Tamir Duberstein" <tamird@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Pedro Yudi Honda" <niyudi.honda@usp.br>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, nova-gpu@lists.linux.de
Subject: Re: [PATCH 0/1] nova-core: Convert bindings to use zerocopy
Date: Mon, 29 Jun 2026 18:05:39 +1000 [thread overview]
Message-ID: <akIlXpFeexxttlV_@nvdebian.thelocal> (raw)
In-Reply-To: <DJLCF3LR0KMN.1TMKMZEZWKN8O@nvidia.com>
On 2026-06-29 at 17:09 +1000, Alexandre Courbot <acourbot@nvidia.com> wrote...
> On Mon Jun 29, 2026 at 2:55 PM JST, SeungJong Ha wrote:
> > On Mon Jun 29, 2026 at 2:52 AM UTC, Alistair Popple wrote:
> >> Given the inevitable conflicts that will arise from trying to merge several
> >> different series doing bits of the same thing I'm happy if someone wants to take
> >> this patch and the others and roll them into a single series. Alternatively I am
> >> happy to take that on - hopefully Alex can provide some guidance here for what
> >> would be preferred.
> >
> > Agreed it should be one series. Happy to help or fold in my part --
> > whatever Alex prefers.
>
> Since there is no particular urgency to switch from transmute to
> zerocopy, I think it makes sense to merge things in an order that limits
> churn as much as possible.
>
> This means the conversion should probably be done bottom-to-top,
> starting with the bindings, then the types that embed them. For the
> bindings, `#[derive(zerocopy_derive::most_traits)]` should be landing
> soon [1] and I would like us to understand first whether that is
> something we want to use with the bindings; if so, let's wait for it to
> be available (unless there is a good reason to convert quickly) as each
> change to `bindings.rs` is almost 200 LoCs.
I think it makes sense to wait, if only to avoid churn on the generated
bindings.
> Since Alistair maintains the tool generating the bindings [2], I think
> it would make sense if he takes care of that part (bindings and anything
> embedding them) as well.
Agreed.
> There are also types in nova-core that do not depend on bindings at all;
> for these I think it is fine to take the patches that have been already
> submitted if they apply cleanly and build, as these are good
> opportunities for first contributions. Nicolás was first to send
> something for vbios/firmware [3] so I'd like to consider his v2 first
> now that `-rc1` is tagged.
Yep - given the interest from other contributors I'm going to leave all the
non-binding related conversions alone. In other words anything that does not
require changes to drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs would be
good for others to look at, and thanks for the contributions!
- Alistair
> For the rest, I'm happy to merge anything that applies - small patches
> limited to a single module should be easier to process and less likely
> to conflict.
>
> [1] https://lore.kernel.org/all/20260625231919.692444-1-ojeda@kernel.org/
> [2] https://github.com/apopple-nvidia/nova-gsp-binding-generator/
> [3] https://lore.kernel.org/all/20260621143647.264770-1-nico.antinori.7@gmail.com/
next prev parent reply other threads:[~2026-06-29 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 2:52 [PATCH 0/1] nova-core: Convert bindings to use zerocopy Alistair Popple
2026-06-29 2:52 ` [PATCH 1/1] nova-core: Update firmware bindings to use zerocopy traits Alistair Popple
2026-06-29 7:36 ` Alexandre Courbot
2026-06-29 7:56 ` Alistair Popple
2026-06-29 9:21 ` Miguel Ojeda
2026-06-29 9:45 ` Alexandre Courbot
2026-06-29 5:55 ` [PATCH 0/1] nova-core: Convert bindings to use zerocopy SeungJong Ha
2026-06-29 7:09 ` Alexandre Courbot
2026-06-29 8:05 ` Alistair Popple [this message]
2026-06-29 8:46 ` 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=akIlXpFeexxttlV_@nvdebian.thelocal \
--to=apopple@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=engineer.jjhama@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nico.antinori.7@gmail.com \
--cc=niyudi.honda@usp.br \
--cc=nova-gpu@lists.linux.de \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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.