From: Alex Williamson <alex@shazbot.org>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: David Matlack <dmatlack@google.com>,
Vipin Sharma <vipinsh@google.com>,
Josh Hilke <jrhilke@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
alex@shazbot.org
Subject: Re: [PATCH v2] vfio/pci: Use a private flag to prevent power state change with VFs
Date: Fri, 22 May 2026 16:39:51 -0600 [thread overview]
Message-ID: <20260522163951.4ba46ec6@shazbot.org> (raw)
In-Reply-To: <20260514173449.3282188-1-rananta@google.com>
On Thu, 14 May 2026 17:34:49 +0000
Raghavendra Rao Ananta <rananta@google.com> wrote:
> The current implementation uses pci_num_vf() while holding the
> memory_lock to prevent changing the power state of a PF when
> VFs are enabled. This creates a lockdep circular dependency
> warning because memory_lock is held during device probing.
>
...
>
> Introduce a private flag 'sriov_active' in the vfio_pci_core_device
> struct. This allows the driver to track the SR-IOV power state requirement
> without relying on pci_num_vf() while holding the memory_lock. The lock is
> now only held to set the flag and ensure the device is in D0, after which
> pci_enable_sriov() can be called without the lock.
>
> Fixes: f4162eb1e2fc ("vfio/pci: Change the PF power state to D0 before enabling VFs")
> Cc: stable@vger.kernel.org
> Suggested-by: Jason Gunthorpe <jgg@ziepe.ca>
> Suggested-by: Alex Williamson <alex@shazbot.org>
> Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
> ---
> drivers/vfio/pci/vfio_pci_core.c | 17 ++++++++++++++---
> include/linux/vfio_pci_core.h | 1 +
> 2 files changed, 15 insertions(+), 3 deletions(-)
Applied to vfio next branch for v7.2, with the noted bitfield
conversion. Thanks,
Alex
prev parent reply other threads:[~2026-05-22 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 17:34 Raghavendra Rao Ananta
2026-05-20 18:53 ` Alex Williamson
2026-05-21 3:49 ` Raghavendra Rao Ananta
2026-05-22 22:39 ` Alex Williamson [this message]
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=20260522163951.4ba46ec6@shazbot.org \
--to=alex@shazbot.org \
--cc=dmatlack@google.com \
--cc=jgg@ziepe.ca \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rananta@google.com \
--cc=stable@vger.kernel.org \
--cc=vipinsh@google.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
Powered by JetHome