From: Baolu Lu <baolu.lu@linux.intel.com>
To: Ethan Zhao <haifeng.zhao@linux.intel.com>,
kevin.tian@intel.com, bhelgaas@google.com, dwmw2@infradead.org,
will@kernel.org, robin.murphy@arm.com, lukas@wunner.de
Cc: baolu.lu@linux.intel.com, linux-pci@vger.kernel.org,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v10 3/5] PCI: make pci_dev_is_disconnected() helper public for other drivers
Date: Wed, 10 Jan 2024 13:25:46 +0800 [thread overview]
Message-ID: <8250acd8-4013-487d-9b31-102334ff316a@linux.intel.com> (raw)
In-Reply-To: <20231228170504.720794-1-haifeng.zhao@linux.intel.com>
On 12/29/23 1:05 AM, Ethan Zhao wrote:
> Make pci_dev_is_disconnected() public so that it can be called from
> Intel VT-d driver to quickly fix/workaround the surprise removal
> unplug hang issue for those ATS capable devices on PCIe switch downstream
> hotplug capable ports.
>
> Beside pci_device_is_present() function, this one has no config space
> space access, so is light enough to optimize the normal pure surprise
> removal and safe removal flow.
>
> Tested-by: Haorong Ye<yehaorong@bytedance.com>
> Signed-off-by: Ethan Zhao<haifeng.zhao@linux.intel.com>
> ---
> drivers/pci/pci.h | 5 -----
> include/linux/pci.h | 5 +++++
> 2 files changed, 5 insertions(+), 5 deletions(-)
This should be moved before PATCH 2/5? Otherwise, PATCH 2/5 couldn't be
compiled.
Best regards,
baolu
next prev parent reply other threads:[~2024-01-10 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 17:05 [RFC PATCH v10 3/5] PCI: make pci_dev_is_disconnected() helper public for other drivers Ethan Zhao
2023-12-28 17:05 ` [RFC PATCH v10 4/5] iommu/vt-d: don't issue ATS Invalidation request when device is disconnected Ethan Zhao
2024-01-10 5:24 ` Baolu Lu
2024-01-10 8:37 ` Ethan Zhao
2024-01-11 2:24 ` Baolu Lu
2024-01-11 4:16 ` Ethan Zhao
2023-12-28 17:05 ` [RFC PATCH v10 5/5] iommu/vt-d: don't loop for timeout ATS Invalidation request forever Ethan Zhao
2023-12-28 17:10 ` Ethan Zhao
2024-01-10 5:28 ` Baolu Lu
2024-01-10 8:40 ` Ethan Zhao
2024-01-11 2:31 ` Baolu Lu
2024-01-11 3:44 ` Ethan Zhao
2024-01-11 6:09 ` Ethan Zhao
2024-01-11 7:44 ` Ethan Zhao
2024-01-10 5:25 ` Baolu Lu [this message]
2024-01-10 8:47 ` [RFC PATCH v10 3/5] PCI: make pci_dev_is_disconnected() helper public for other drivers Ethan Zhao
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=8250acd8-4013-487d-9b31-102334ff316a@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dwmw2@infradead.org \
--cc=haifeng.zhao@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=robin.murphy@arm.com \
--cc=will@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