From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Gary Guo" <gary@kernel.org>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.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>,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: nova-core: move lifetime to `Bar0`
Date: Wed, 03 Jun 2026 19:47:02 +0900 [thread overview]
Message-ID: <DIZCROA18EVK.1WTOC61CIP7Y2@nvidia.com> (raw)
In-Reply-To: <20260602170416.2268531-1-gary@kernel.org>
On Wed Jun 3, 2026 at 2:04 AM JST, Gary Guo wrote:
> From: Gary Guo <gary@garyguo.net>
>
> Currently Nova code uses `&'a Bar0` a lot. This is `&'a Mmio`, where `Mmio`
> represents an owned MMIO region; this type only exists as a target for
> `Deref` so `Bar` and `IoMem` can share code and should be avoided to be
> named directly. The upcoming I/O projection series would make `Io` trait
> much simpler to implement, and thuis the owned MMIO type would be removed
> in favour of direct `Io` implementation on `Bar` and `IoMem`.
>
> Add lifetime parameter to `Bar0<'a>` and change it to be alias of `&'a
> pci::Bar<'a, ..>`. This also prepares Nova core so that when I/O projection
> series land, this could be changed to using a MMIO view type directly which
> avoids double indirection.
>
> Signed-off-by: Gary Guo <gary@garyguo.net>
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
next prev parent reply other threads:[~2026-06-03 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 17:04 [PATCH] gpu: nova-core: move lifetime to `Bar0` Gary Guo
2026-06-03 1:58 ` Eliot Courtney
2026-06-03 10:47 ` Alexandre Courbot [this message]
2026-06-03 22:52 ` 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=DIZCROA18EVK.1WTOC61CIP7Y2@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=gary@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
/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.