From: Alex Williamson <alex.williamson@nvidia.com>
To: kvm <kvm@vger.kernel.org>, Alex Williamson <alex@shazbot.org>
Cc: Alex Williamson <alex.williamson@nvidia.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
kanie@linux.alibaba.com
Subject: [PATCH 0/2] vfio/pci: Latch module parameters per device
Date: Thu, 11 Jun 2026 12:25:24 -0600 [thread overview]
Message-ID: <20260611182528.4004073-1-alex.williamson@nvidia.com> (raw)
The vfio-pci module pushes module parameters into vfio-pci-core at
initialization that change global policies for all devices, bound to
vfio-pci itself or other variant drivers. Not only is this generally bad
practice, but in the case of runtime PM, policy changes can affect
initialized devices, even while they're in use, resulting in unbalanced
operations.
This series first addresses the runtime PM case as a separate fix for
stable, latching the runtime PM support into the device. It then
expands the scope to pull the policy set by vfio-pci out of the core,
making each policy latched at the device by the variant driver.
This also has the effect of restoring the mutability of two of the module
parameters, where that functionality was lost with the vfio-pci-core
split. With this series, the current parameter values are latched into
the device at probe time.
Please review. Thanks,
Alex
Alex Williamson (2):
vfio/pci: Latch disable_idle_d3 per device
vfio/pci: Latch all module parameters per device
drivers/vfio/pci/vfio_pci.c | 30 +++++++++++++-----
drivers/vfio/pci/vfio_pci_core.c | 52 +++++++++++++++-----------------
include/linux/vfio_pci_core.h | 5 +--
3 files changed, 49 insertions(+), 38 deletions(-)
--
2.53.0
next reply other threads:[~2026-06-11 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 18:25 Alex Williamson [this message]
2026-06-11 18:25 ` [PATCH 1/2] vfio/pci: Latch disable_idle_d3 " Alex Williamson
2026-06-11 18:25 ` [PATCH 2/2] vfio/pci: Latch all module parameters " Alex Williamson
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=20260611182528.4004073-1-alex.williamson@nvidia.com \
--to=alex.williamson@nvidia.com \
--cc=alex@shazbot.org \
--cc=jgg@ziepe.ca \
--cc=kanie@linux.alibaba.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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®