From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: mani@kernel.org
Cc: alex@shazbot.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org, bhelgaas@google.com,
jjohnson@kernel.org, jtornosm@redhat.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-wireless@vger.kernel.org, mhi@lists.linux.dev
Subject: Re: [PATCH v9] PCI: Add device-specific reset for Qualcomm devices
Date: Wed, 17 Jun 2026 17:47:04 +0200 [thread overview]
Message-ID: <20260617154709.186286-1-jtornosm@redhat.com> (raw)
In-Reply-To: <6nivb5fncfd5dwqkzlxwhtgbsiqvifazcbgpsgukp44iib45ke@65qpwgrvtkgn>
Hi Mani,
Thank you for the internal clarification and sharing this information.
I understand the behavior is firmware error recovery, not a proper reset.
However, these devices are widely used, and the inability to use them in VMs
is a significant problem. Could we explore options to achieve safe VFIO
operation?
1. Are there ANY alternative reset mechanisms besides D3cold? For example:
- Device-specific registers or commands?
- MHI bus-level operations?
- Firmware commands that could trigger proper reset?
If such mechanisms exist, I'm willing to implement whatever is needed.
2. If firmware error recovery is the only option available on platforms
without _PR3, could we add software steps to make it VFIO-safe?
For example, before/after the D3hot transition:
- Explicit MHI state teardown?
- Firmware commands to clear sensitive device state?
- Additional verification or cleanup steps?
3. The practical challenge is that _PR3 support is not available on most
platforms where these devices need to be deployed (desktops, servers).
Additionally, the general d3cold reset method has limitations and
remains unimplemented due to the concerns raised earlier (ACPI
portability, bridge issues, runtime PM complications).
If D3cold is the only proper reset but requires _PR3, and no alternative
mechanisms exist, could we consider accepting the firmware error recovery
behavior as a last resort - clearly documented as a platform-specific
workaround?
Currently these devices have no reset capability on most platforms,
making them completely unusable for VFIO. Even an imperfect reset is
significantly better than no reset at all.
My goal is ensuring these devices can be safely reassigned between VMs.
I'm open to implementing any of the above approaches - or others you might
suggest.
Thank you
Best regards
José Ignacio
next prev parent reply other threads:[~2026-06-17 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 14:26 [PATCH v9] PCI: Add device-specific reset for Qualcomm devices Jose Ignacio Tornos Martinez
2026-06-12 15:12 ` Alex Williamson
2026-06-12 15:17 ` Bjorn Helgaas
2026-06-15 7:30 ` Jose Ignacio Tornos Martinez
2026-06-17 14:47 ` Manivannan Sadhasivam
2026-06-17 15:47 ` Jose Ignacio Tornos Martinez [this message]
2026-06-17 16:55 ` Manivannan Sadhasivam
2026-06-18 6:33 ` Jose Ignacio Tornos Martinez
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=20260617154709.186286-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=alex@shazbot.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
/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