From: Simon Song <xinmengs@nvidia.com>
To: <dakr@kernel.org>, <acourbot@nvidia.com>, <kvm@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>, <nova-gpu@lists.linux.dev>,
<linux-pci@vger.kernel.org>
Cc: <alex@shazbot.org>, <jgg@nvidia.com>, <yishaih@nvidia.com>,
<skolothumtho@nvidia.com>, <kevin.tian@intel.com>,
<airlied@gmail.com>, <simona@ffwll.ch>, <ojeda@kernel.org>,
<alex.gaynor@gmail.com>, <boqun.feng@gmail.com>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <a.hindborg@kernel.org>,
<aliceryhl@google.com>, <tmgross@umich.edu>,
<jhubbard@nvidia.com>, <ecourtney@nvidia.com>, <cjia@nvidia.com>,
<smitra@nvidia.com>, <kjaju@nvidia.com>, <alkumar@nvidia.com>,
<ankita@nvidia.com>, <aniketa@nvidia.com>, <kwankhede@nvidia.com>,
<targupta@nvidia.com>, <linux-kernel@vger.kernel.org>,
<zhiwang@kernel.org>, <zhiw@nvidia.com>, <boqun@kernel.org>,
<daniel.almeida@collabora.com>, <tamird@kernel.org>,
<work@onurozkan.dev>, <jgg@ziepe.ca>, <bhelgaas@google.com>,
<kwilczynski@kernel.org>, <dri-devel@lists.freedesktop.org>,
<peter@colberg.org>, <xinmengs@nvidia.com>
Subject: [PATCH v2 08/12] rust: pci: add runtime PM callbacks
Date: Fri, 23 Oct 2026 08:40:03 -0700 [thread overview]
Message-ID: <20261023154009.2246627-9-xinmengs@nvidia.com> (raw)
In-Reply-To: <20261023154009.2246627-1-xinmengs@nvidia.com>
VFIO PCI variant drivers will use runtime_suspend() and runtime_resume()
to forward runtime PM callbacks to vfio-pci-core.
Adding these callbacks to pci::Driver lets VFIO variants reuse the PCI
adapter's runtime PM callback dispatch. A following patch removes the
duplicate vfio::pci::Adapter.
Require Sync driver data only for runtime PM, whose callbacks run
without the PCI device lock.
Suggested-by: Zhi Wang <zhiw@nvidia.com>
Signed-off-by: Simon Song <xinmengs@nvidia.com>
---
rust/kernel/pci.rs | 103 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 103 insertions(+)
diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
index ddc28099087..136a817a833 100644
--- a/rust/kernel/pci.rs
+++ b/rust/kernel/pci.rs
@@ -112,6 +112,10 @@ unsafe fn register(
if T::HAS_ERROR_DETECTED || T::HAS_RESET_PREPARE || T::HAS_RESET_DONE {
(*pdrv.get()).err_handler = &Self::ERROR_HANDLERS;
}
+ #[cfg(CONFIG_PM)]
+ if let Some(ops) = T::PM_OPS {
+ (*pdrv.get()).driver.pm = ops.raw;
+ }
#[cfg(CONFIG_PCI_IOV)]
if T::HAS_SRIOV_ENABLE {
(*pdrv.get()).sriov_configure = Some(Self::sriov_configure_callback);
@@ -261,6 +265,72 @@ extern "C" fn error_detected_callback(
};
}
+#[cfg(CONFIG_PM)]
+impl<T: Driver> Adapter<T>
+where
+ for<'a> T::Data<'a>: Sync,
+{
+ extern "C" fn runtime_suspend_callback(dev: *mut bindings::device) -> c_int {
+ // SAFETY: PCI supplies its embedded device; runtime PM excludes driver-data removal.
+ let pdev =
+ unsafe { &*container_of!(dev, bindings::pci_dev, dev).cast::<Device<device::Bound>>() };
+ // SAFETY: Runtime PM keeps installed data alive; `T::Data: Sync` permits shared borrows.
+ let result =
+ unsafe { Self::callback_data_with(dev, |data| T::runtime_suspend(pdev, data)) }
+ .unwrap_or(Err(EBUSY));
+ match result {
+ Ok(()) => 0,
+ Err(error) => error.to_errno(),
+ }
+ }
+
+ extern "C" fn runtime_resume_callback(dev: *mut bindings::device) -> c_int {
+ // SAFETY: PCI supplies its embedded device; runtime PM excludes driver-data removal.
+ let pdev =
+ unsafe { &*container_of!(dev, bindings::pci_dev, dev).cast::<Device<device::Bound>>() };
+ // SAFETY: Runtime PM keeps installed data alive; `T::Data: Sync` permits shared borrows.
+ let result = unsafe { Self::callback_data_with(dev, |data| T::runtime_resume(pdev, data)) }
+ .unwrap_or(Err(ENODEV));
+ match result {
+ Ok(()) => 0,
+ Err(error) => error.to_errno(),
+ }
+ }
+
+ const PM_OPS: bindings::dev_pm_ops = bindings::dev_pm_ops {
+ runtime_suspend: Some(Self::runtime_suspend_callback),
+ runtime_resume: Some(Self::runtime_resume_callback),
+ ..pin_init::zeroed()
+ };
+}
+
+/// Runtime PM callbacks for PCI driver `T`, installed through [`Driver::PM_OPS`].
+#[cfg(CONFIG_PM)]
+pub struct PmOps<T: ?Sized> {
+ raw: &'static bindings::dev_pm_ops,
+ // Invariant in `T`, so subtyping can't pass one driver's callbacks off as another's.
+ _driver: PhantomData<fn(&T) -> &T>,
+}
+
+#[cfg(CONFIG_PM)]
+impl<T: Driver> PmOps<T>
+where
+ for<'a> T::Data<'a>: Sync,
+{
+ /// Returns the runtime PM callbacks for `T`, which must override both PM methods.
+ #[expect(clippy::new_without_default)]
+ pub const fn new() -> Self {
+ const_assert!(
+ T::HAS_RUNTIME_SUSPEND && T::HAS_RUNTIME_RESUME,
+ "PCI runtime PM requires both runtime_suspend and runtime_resume"
+ );
+ Self {
+ raw: &Adapter::<T>::PM_OPS,
+ _driver: PhantomData,
+ }
+ }
+}
+
/// Declares a kernel module that exposes a single PCI driver.
///
/// # Examples
@@ -425,6 +495,9 @@ pub trait Driver {
type IdInfo: 'static;
/// The type of the driver's bus device private data.
+ ///
+ /// Callbacks access this data under the PCI device lock, except runtime PM callbacks,
+ /// which additionally require [`Sync`].
type Data<'bound>: Send + 'bound;
/// The table of device ids supported by the driver.
@@ -462,6 +535,9 @@ fn bind<'bound>(dev: &Device<device::Core<'_>>, this: Pin<&Self::Data<'bound>>)
///
/// Otherwise, release operations for driver resources should be performed in `Drop`.
///
+ /// PCI has drained runtime-PM work before this callback. Driver data remains installed
+ /// until this callback returns.
+ ///
/// For a PF with enabled VFs, `VfRegistration` disables SR-IOV when it is dropped. This
/// callback must leave resources accessed by VF drivers available until then.
fn unbind<'bound>(dev: &'bound Device<device::Core<'_>>, this: Pin<&Self::Data<'bound>>) {
@@ -490,6 +566,33 @@ fn error_detected<'bound>(
build_error!(crate::error::VTABLE_DEFAULT_ERROR)
}
+ /// Prepare for runtime suspend, without holding the PCI device lock.
+ #[cfg(CONFIG_PM)]
+ fn runtime_suspend<'bound>(
+ dev: &Device<device::Bound>,
+ this: Pin<&Self::Data<'bound>>,
+ ) -> Result
+ where
+ for<'a> Self::Data<'a>: Sync,
+ {
+ let _ = (dev, this);
+ build_error!(crate::error::VTABLE_DEFAULT_ERROR)
+ }
+
+ /// Finish runtime resume, without holding the PCI device lock.
+ #[cfg(CONFIG_PM)]
+ fn runtime_resume<'bound>(dev: &Device<device::Bound>, this: Pin<&Self::Data<'bound>>) -> Result
+ where
+ for<'a> Self::Data<'a>: Sync,
+ {
+ let _ = (dev, this);
+ build_error!(crate::error::VTABLE_DEFAULT_ERROR)
+ }
+
+ /// Runtime PM callbacks, if any. Construct with [`PmOps::new`].
+ #[cfg(CONFIG_PM)]
+ const PM_OPS: Option<PmOps<Self>> = None;
+
/// Enables Single Root I/O Virtualization (SR-IOV) for a PF.
///
/// Called when userspace writes a nonzero VF count to `sriov_numvfs`. The token carries the
--
2.43.7
next prev parent reply other threads:[~2026-10-23 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 15:39 [PATCH v2 00/12] Rust VFIO PCI support and NVIDIA vGPU driver Simon Song
2026-10-23 15:39 ` [PATCH v2 01/12] rust: pci: add VFIO override device IDs Simon Song
2026-10-23 20:07 ` Gary Guo
2026-10-23 15:39 ` [PATCH v2 02/12] rust: pci: expose the VF index within its PF Simon Song
2026-10-23 15:39 ` [PATCH v2 03/12] rust: pci: allow drivers to manage DMA ownership Simon Song
2026-10-23 15:39 ` [PATCH v2 04/12] rust: vfio: add PCI variant driver abstractions Simon Song
2026-10-23 15:40 ` [PATCH v2 05/12] rust: pci: add reset callbacks Simon Song
2026-10-23 15:40 ` [PATCH v2 06/12] rust: pci: add a bind callback after installing driver data Simon Song
2026-10-23 15:40 ` [PATCH v2 07/12] rust: pci: add an error_detected callback Simon Song
2026-10-23 15:40 ` Simon Song [this message]
2026-10-23 15:40 ` [PATCH v2 09/12] rust: vfio: use the PCI adapter for variant drivers Simon Song
2026-10-23 15:40 ` [PATCH v2 10/12] rust: vfio: separate common device handling from PCI Simon Song
2026-10-23 15:40 ` [PATCH v2 11/12] gpu: nova-core: publish typed SR-IOV PF APIs Simon Song
2026-10-23 15:40 ` [PATCH v2 12/12] vfio/nvidia-vgpu: add the Rust VFIO variant driver Simon Song
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=20261023154009.2246627-9-xinmengs@nvidia.com \
--to=xinmengs@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.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.feng@gmail.com \
--cc=boqun@kernel.org \
--cc=cjia@nvidia.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kjaju@nvidia.com \
--cc=kvm@vger.kernel.org \
--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=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=peter@colberg.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=skolothumtho@nvidia.com \
--cc=smitra@nvidia.com \
--cc=tamird@kernel.org \
--cc=targupta@nvidia.com \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=yishaih@nvidia.com \
--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 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®