mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: helgaas@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, mani@kernel.org,
	mhi@lists.linux.dev
Subject: Re: [PATCH v13] PCI: Add device-specific reset for Qualcomm devices
Date: Fri, 18 Sep 2026 08:29:01 +0200	[thread overview]
Message-ID: <20260918062901.7578-1-jtornosm@redhat.com> (raw)
In-Reply-To: <20260917170642.GA1026691@bhelgaas>

Hi Bjorn,

> Ah, so this depends on the previous VM tenant to clean up
> after itself instead of the host kernel enforcing the
> isolation?

That is actually the current situation without this patch, there is no
working reset method, and since it depends on the previous status, the
host cannot enforce isolation at all.

This patch adds a hardware reset that the host uses on every device
reassignment (device-specific reset is position #1 in the reset hierarchy),
regardless of how the previous VM terminated. It improves isolation by
giving the host a real reset mechanism where none exists today.

The clean/unclean distinction was only explaining why things happen to work
today without a reset in some cases, not a limitation of the proposed reset.

Thanks

Best regards
Jose Ignacio


  reply	other threads:[~2026-09-18  6:29 UTC|newest]

Thread overview: 9+ 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
2026-09-18  6:29       ` Jose Ignacio Tornos Martinez [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=20260918062901.7578-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=helgaas@kernel.org \
    --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

all inboxes | Powered by JetHome®