From: Alice Ryhl <aliceryhl@google.com>
To: Deborah Brouwer <deborah.brouwer@collabora.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] rust/Makefile: add zerocopy and zerocopy_derive
Date: Tue, 20 Oct 2026 08:01:06 +0000 [thread overview]
Message-ID: <20261020080106.1742330-1-aliceryhl@google.com> (raw)
In-Reply-To: <20261019-b4-gpu_info_intobytes-v4-1-0bc04df46549@collabora.com>
On Mon, Oct 19, 2026 at 04:25:59PM -0700, Deborah Brouwer wrote:
> Make the zerocopy and zerocopy_derive crates available for use when
> building the bindings and uapi crates and their tests.
>
> This will be used by the Tyr driver that needs the traits IntoBytes and
> Immutable to safely copy the struct byte-for-byte to userspace.
>
> Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
> ---
> rust/Makefile | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
`scripts/generate_rust_analyzer.py` also needs to pass `zerocopy` and
`zerocopy_derive` in the `deps` lists of `bindings` and `uapi` (similar
to commit 3c847e17225a ("rust: add `pin-init` as a dependency to
`bindings` and `uapi`")).
Without that update, `make rust-analyzer` generates a `rust-project.json`
where `bindings` and `uapi` only depend on `core`, `ffi`, and `pin_init`,
so `rust-analyzer` fails to resolve `zerocopy_derive::most_traits` in
`uapi` and does not see the derived traits on `drm_panthor_gpu_info` in
`tyr`.
With `scripts/generate_rust_analyzer.py` updated as well, a subject
prefix like `rust: add zerocopy and zerocopy_derive to bindings and uapi`
might fit better too.
> diff --git a/rust/Makefile b/rust/Makefile
> index da1a7409d984..f59815fac293 100644
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@ -361,12 +361,18 @@ rusttestlib-kernel: $(src)/kernel/lib.rs rusttestlib-bindings rusttestlib-uapi \
> $(obj)/bindings.o rusttestlib-zerocopy rusttestlib-zerocopy_derive FORCE
> +$(call if_changed,rustc_test_library)
>
> -rusttestlib-bindings: private rustc_target_flags = --extern ffi --extern pin_init
> -rusttestlib-bindings: $(src)/bindings/lib.rs rusttestlib-ffi rusttestlib-pin_init FORCE
> +rusttestlib-bindings: private rustc_target_flags = --extern ffi --extern pin_init \
> + --extern zerocopy=$(objtree)/$(obj)/test/libzerocopy.rlib \
> + --extern zerocopy_derive=$(objtree)/$(obj)/test/$(libzerocopy_derive_name)
> +rusttestlib-bindings: $(src)/bindings/lib.rs rusttestlib-ffi rusttestlib-pin_init \
> + rusttestlib-zerocopy rusttestlib-zerocopy_derive FORCE
> +$(call if_changed,rustc_test_library)
Nit: non-recipe continuation lines in `rust/Makefile` use 4 spaces for
indentation rather than tabs (same for `rusttestlib-uapi`,
`$(obj)/bindings.o`, and `$(obj)/uapi.o` below).
Alice
next prev parent reply other threads:[~2026-10-20 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 23:25 [PATCH v4 0/2] drm/tyr: safely write GpuInfo to userspace Deborah Brouwer
2026-10-19 23:25 ` [PATCH v4 1/2] rust/Makefile: add zerocopy and zerocopy_derive Deborah Brouwer
2026-10-20 8:01 ` Alice Ryhl [this message]
2026-10-19 23:26 ` [PATCH v4 2/2] drm/tyr: safely write GpuInfo to userspace Deborah Brouwer
2026-10-20 8:01 ` Alice Ryhl
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=20261020080106.1742330-1-aliceryhl@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--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 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®