From: "Danilo Krummrich" <dakr@kernel.org>
To: "Zhi Wang" <zhiw@nvidia.com>
Cc: <rust-for-linux@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <aliceryhl@google.com>,
<bhelgaas@google.com>, <kwilczynski@kernel.org>,
<ojeda@kernel.org>, <boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <tmgross@umich.edu>,
<markus.probst@posteo.de>, <cjia@nvidia.com>, <smitra@nvidia.com>,
<ankita@nvidia.com>, <aniketa@nvidia.com>, <kwankhede@nvidia.com>,
<targupta@nvidia.com>, <kjaju@nvidia.com>, <alkumar@nvidia.com>,
<acourbot@nvidia.com>, <jhubbard@nvidia.com>,
<zhiwang@kernel.org>, <jgg@nvidia.com>, <alex@shazbot.org>,
"Peter Colberg" <peter@colberg.org>
Subject: Re: [PATCH v3 08/10] rust: pci: add SR-IOV enable and disable tokens
Date: Wed, 30 Sep 2026 16:25:36 +0200 [thread overview]
Message-ID: <DLSPXUPSF0TC.3PC9F8RTDV1IL@kernel.org> (raw)
In-Reply-To: <9b092d339961f744c7ded1e4f21911b66c80ecb4.1790759932.git.zhiw@nvidia.com>
On Wed Sep 30, 2026 at 12:18 PM CEST, Zhi Wang wrote:
> +pub struct SriovEnable<'callback> {
I understand why you chose 'callback, but I think just 'a is good enough.
> + pdev: &'callback Device<device::CoreInternal<'callback>>,
> + num_vfs: u32,
Please see patch 1.
> +}
> +
> +impl<'callback> SriovEnable<'callback> {
> + /// Returns the number of VFs requested for this callback.
> + pub fn num_vfs(&self) -> u32 {
> + self.num_vfs
> + }
> +
> + /// Enables between one and the requested number of VFs.
> + ///
> + /// VF drivers can probe before this method returns, so the PF resources they access must
> + /// already be initialized. The returned guard disables the VFs if subsequent setup fails.
> + /// Return it from `sriov_enable()` to leave the VFs enabled on callback success.
> + pub fn enable(self, num_vfs: u32) -> Result<SriovEnabled<'callback>> {
> + if num_vfs == 0 || num_vfs > self.num_vfs {
> + return Err(EINVAL);
> + }
> + let num_vfs = c_int::try_from(num_vfs).map_err(|_| EOVERFLOW)?;
> +
> + // SAFETY: The PF's driver data and registration remain installed throughout this callback.
> + // The registration owns final VF teardown after the enable guard is disarmed.
> + if unsafe { (*self.pdev.as_raw()).vf_registration_data_rust }.is_null() {
> + return Err(ENODEV);
> + }
> +
> + self.pdev.enable_sriov(num_vfs)?;
> + Ok(SriovEnabled {
> + pdev: Some(self.pdev),
> + num_vfs,
> + })
> + }
> +}
> +
> +/// Enabled VFs awaiting successful completion of `sriov_enable()`.
> +pub struct SriovEnabled<'callback> {
> + pdev: Option<&'callback Device<device::CoreInternal<'callback>>>,
This doesn't need to be an Option.
> + num_vfs: c_int,
> +}
> +
> +impl SriovEnabled<'_> {
> + #[expect(dead_code)]
> + fn disarm(mut self) -> c_int {
> + self.pdev = None;
> + self.num_vfs
Instead of the Option dance, you can use ManuallyDrop to prevent the destructor
from running.
> + }
> +}
> +
> +impl Drop for SriovEnabled<'_> {
> + fn drop(&mut self) {
> + if let Some(pdev) = self.pdev.take() {
> + pdev.disable_sriov();
> + }
> + }
> +}
next prev parent reply other threads:[~2026-09-30 14:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:18 [PATCH v3 00/10] Add Rust PCI SR-IOV support Zhi Wang
2026-09-30 10:18 ` [PATCH v3 01/10] rust: pci: add internal SR-IOV enable and disable helpers Zhi Wang
2026-09-30 10:34 ` sashiko-bot
2026-09-30 10:58 ` Danilo Krummrich
2026-09-30 10:18 ` [PATCH v3 02/10] rust: pci: add vtable attribute to pci::Driver trait Zhi Wang
2026-09-30 10:36 ` sashiko-bot
2026-09-30 10:18 ` [PATCH v3 03/10] rust: pci: add is_virtfn(), to check for VFs Zhi Wang
2026-09-30 10:34 ` sashiko-bot
2026-09-30 10:18 ` [PATCH v3 04/10] rust: pci: add is_physfn(), to check for PFs Zhi Wang
2026-09-30 10:30 ` sashiko-bot
2026-09-30 10:18 ` [PATCH v3 05/10] rust: pci: add num_vf(), to return number of VFs Zhi Wang
2026-09-30 10:32 ` sashiko-bot
2026-09-30 11:13 ` Danilo Krummrich
2026-10-03 17:12 ` Zhi Wang
2026-09-30 10:18 ` [PATCH v3 06/10] rust: pci: drop driver data before remove returns Zhi Wang
2026-09-30 10:35 ` sashiko-bot
2026-09-30 10:18 ` [PATCH v3 07/10] rust: pci: add typed SR-IOV PF registration data Zhi Wang
2026-09-30 10:36 ` sashiko-bot
2026-09-30 13:59 ` Danilo Krummrich
2026-10-04 6:07 ` Zhi Wang
2026-09-30 10:18 ` [PATCH v3 08/10] rust: pci: add SR-IOV enable and disable tokens Zhi Wang
2026-09-30 10:37 ` sashiko-bot
2026-09-30 14:25 ` Danilo Krummrich [this message]
2026-10-04 6:16 ` Zhi Wang
2026-09-30 10:18 ` [PATCH v3 09/10] rust: pci: add SR-IOV enable and disable callbacks Zhi Wang
2026-09-30 10:37 ` sashiko-bot
2026-09-30 14:46 ` Danilo Krummrich
2026-09-30 10:18 ` [PATCH v3 10/10] samples: rust: add Rust SR-IOV VF driver sample Zhi Wang
2026-09-30 10:46 ` sashiko-bot
2026-09-30 15:15 ` Danilo Krummrich
2026-10-04 6:21 ` Zhi Wang
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=DLSPXUPSF0TC.3PC9F8RTDV1IL@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alex@shazbot.org \
--cc=aliceryhl@google.com \
--cc=alkumar@nvidia.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=cjia@nvidia.com \
--cc=gary@garyguo.net \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=kjaju@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=peter@colberg.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=smitra@nvidia.com \
--cc=targupta@nvidia.com \
--cc=tmgross@umich.edu \
--cc=zhiw@nvidia.com \
--cc=zhiwang@kernel.org \
/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.