From: sashiko-bot@kernel.org
To: "Zhi Wang" <zhiw@nvidia.com>
Cc: ojeda@kernel.org, linux-pci@vger.kernel.org, gary@garyguo.net
Subject: Re: [PATCH v4 7/9] rust: pci: add SR-IOV enable and disable tokens
Date: Sun, 04 Oct 2026 12:17:04 +0000 [thread overview]
Message-ID: <20261004121704.9AA521F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004120732.1045629-8-zhiw@nvidia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] rust: missing #[inline] on small abstraction functions
--
commit e7af204882b55dcbfacee7ce650e2197a9830e0f
Author: Zhi Wang <zhiw@nvidia.com>
rust: pci: add SR-IOV enable and disable tokens
This commit introduces SR-IOV enable and disable tokens for PCI device
drivers in Rust. It utilizes callback-scoped guards to ensure SR-IOV is
disabled on error and coordinates final VF teardown with registration
tokens.
> diff --git a/rust/kernel/pci/iov.rs b/rust/kernel/pci/iov.rs
> index c61462595141f..449f1e9b12fda 100644
> --- a/rust/kernel/pci/iov.rs
> +++ b/rust/kernel/pci/iov.rs
[ ... ]
> +pub struct SriovEnable<'a> {
> + pdev: &'a Device<device::CoreInternal<'a>>,
> + num_vfs: u16,
> +}
> +
> +impl<'a> SriovEnable<'a> {
> + /// Returns the number of VFs requested for this callback.
> + pub fn num_vfs(&self) -> u16 {
> + self.num_vfs
> + }
[Severity: Low]
Should this trivial accessor be annotated with #[inline]? Subsystem
guidelines suggest small functions in the kernel crate abstraction should be
explicitly annotated to prevent suboptimal code generation.
[ ... ]
> +/// Enabled VFs awaiting successful completion of `sriov_enable()`.
> +pub struct SriovEnabled<'a> {
> + pdev: &'a Device<device::CoreInternal<'a>>,
> + num_vfs: u16,
> +}
> +
> +impl SriovEnabled<'_> {
> + #[expect(dead_code)]
> + fn disarm(self) -> u16 {
> + ManuallyDrop::new(self).num_vfs
> + }
[Severity: Low]
Does this small wrapper manipulating object destruction need an #[inline]
annotation to ensure optimal inlining across crate boundaries?
[ ... ]
> +pub struct SriovDisable<'a> {
> + pdev: &'a Device<device::CoreInternal<'a>>,
> +}
> +
> +impl SriovDisable<'_> {
> + /// Disables all VFs and waits for their drivers to unbind.
> + ///
> + /// The PF resources used by VF drivers must remain available until this method returns.
> + pub fn disable(self) {
> + self.pdev.disable_sriov();
> + }
[Severity: Low]
Could this small forwarding method benefit from an #[inline] annotation?
The Rust subsystem guidelines recommend #[inline] for functions forwarding
to other methods in abstractions.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261004120732.1045629-1-zhiw@nvidia.com?part=7
next prev parent reply other threads:[~2026-10-04 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 12:07 [PATCH v4 0/9] Add Rust PCI SR-IOV support Zhi Wang
2026-10-04 12:07 ` [PATCH v4 1/9] rust: pci: add internal SR-IOV enable and disable helpers Zhi Wang
2026-10-04 12:14 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 2/9] rust: pci: add vtable attribute to pci::Driver trait Zhi Wang
2026-10-04 12:12 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 3/9] rust: pci: add is_virtfn(), to check for VFs Zhi Wang
2026-10-04 12:17 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 4/9] rust: pci: add num_vf(), to return number of VFs Zhi Wang
2026-10-04 12:15 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 5/9] rust: pci: drop driver data before remove returns Zhi Wang
2026-10-04 12:15 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 6/9] rust: pci: add typed SR-IOV PF registration data Zhi Wang
2026-10-04 12:20 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 7/9] rust: pci: add SR-IOV enable and disable tokens Zhi Wang
2026-10-04 12:17 ` sashiko-bot [this message]
2026-10-04 12:07 ` [PATCH v4 8/9] rust: pci: add SR-IOV enable and disable callbacks Zhi Wang
2026-10-04 12:22 ` sashiko-bot
2026-10-04 12:07 ` [PATCH v4 9/9] samples: rust: add Rust SR-IOV PF and VF driver samples Zhi Wang
2026-10-04 12:17 ` sashiko-bot
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=20261004121704.9AA521F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhiw@nvidia.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