From: Bjorn Helgaas <helgaas@kernel.org>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: alex@shazbot.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org, bhelgaas@google.com,
jjohnson@kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-wireless@vger.kernel.org,
mani@kernel.org, mhi@lists.linux.dev
Subject: Re: [PATCH v13] PCI: Add device-specific reset for Qualcomm devices
Date: Thu, 17 Sep 2026 12:06:42 -0500 [thread overview]
Message-ID: <20260917170642.GA1026691@bhelgaas> (raw)
In-Reply-To: <20260917065918.13357-1-jtornosm@redhat.com>
On Thu, Sep 17, 2026 at 08:59:18AM +0200, Jose Ignacio Tornos Martinez wrote:
> Hi Bjorn,
>
> Thanks for the review.
>
> > I guess you are saying that some kind of reset *does* work
> > fine in normal, clean VM termination? If reset works fine
> > for normal VM termination but not for VM crash, do we have
> > any idea why they are different?
>
> It depends on the device:
>
> - For the modems (SDX62/SDX65), without a proper reset
> capability, these devices never successfully initialize
> even on first VM assignment.
>
> - For the WLAN devices (WCN6855/WCN7850), the reset fails
> in both cases, but on clean VM shutdown the guest driver's
> .shutdown/.remove callbacks properly deinitialize the device
> (stop DMA, disable interrupts, etc.), so it ends up in a
> known-good state even without a successful reset. On unclean
> termination (crash, force-off), the guest driver callbacks
> never run, the device stays in an undefined state, and
> without a working reset it cannot be reused.
Ah, so this depends on the previous VM tenant to clean up after itself
instead of the host kernel enforcing the isolation?
That seems important to mention and potentially unacceptable to
tenants if an issue in the tenant's kernel may cause their data to be
leaked to the next user of the device.
> I will try to clarify this better in the commit messages for v14.
>
> > Since these basically copy code from other drivers, is there
> > an opportunity to remove it from those drivers and use this
> > instead?
>
> Yes, that could be a follow-up after this lands.
Sounds good.
next prev parent reply other threads:[~2026-09-17 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 8:13 Jose Ignacio Tornos Martinez
2026-07-22 12:21 ` Manivannan Sadhasivam
2026-09-14 12:46 ` Jose Ignacio Tornos Martinez
2026-09-15 22:36 ` Bjorn Helgaas
2026-09-17 6:59 ` Jose Ignacio Tornos Martinez
2026-09-17 17:06 ` Bjorn Helgaas [this message]
[not found] <20260721082933.7B5A41F000E9@smtp.kernel.org>
2026-07-22 11:28 ` Jose Ignacio Tornos Martinez
2026-07-22 12:17 ` Manivannan Sadhasivam
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=20260917170642.GA1026691@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex@shazbot.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=jjohnson@kernel.org \
--cc=jtornosm@redhat.com \
--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
all inboxes | Powered by JetHome®