From: Michael Kelley <mikelley@microsoft.com>
To: sthemmin@microsoft.com, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
rafael@kernel.org, lenb@kernel.org, lorenzo.pieralisi@arm.com,
robh@kernel.org, kw@linux.com, bhelgass@google.com, hch@lst.de,
m.szyprowski@samsung.com, robin.murphy@arm.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: mikelley@microsoft.com
Subject: [PATCH 0/4] Fix coherence for VMbus and PCI pass-thru devices in Hyper-V VM
Date: Thu, 17 Mar 2022 09:12:39 -0700 [thread overview]
Message-ID: <1647533563-2170-1-git-send-email-mikelley@microsoft.com> (raw)
Hyper-V VMs have VMbus synthetic devices and PCI pass-thru devices that are added
dynamically via the VMbus protocol and are not represented in the ACPI DSDT. Only
the top level VMbus node exists in the DSDT. As such, on ARM64 these devices don't
pick up coherence information and default to not hardware coherent. This results
in extra software coherence management overhead since the synthetic devices are
always hardware coherent. PCI pass-thru devices are also hardware coherent in all
current usage scenarios.
Fix this by propagating coherence information from the top level VMbus node in
the DSDT to all VMbus synthetic devices and PCI pass-thru devices. While smaller
granularity of control would be better, basing on the VMbus node in the DSDT
gives as escape path if a future scenario arises with devices that are not
hardware coherent.
The first two patches are prep to allow manipulating device coherence from a
module (since the VMbus driver can be built as a module) and from architecture
independent code without having a bunch of #ifdef's.
The third patch propagates the VMbus node coherence to VMbus synthetic devices.
The fourth patch propagates the coherence to PCI pass-thru devices.
Michael Kelley (4):
ACPI: scan: Export acpi_get_dma_attr()
dma-mapping: Add wrapper function to set dma_coherent
Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device
PCI: hv: Propagate coherence from VMbus device to PCI device
drivers/acpi/scan.c | 1 +
drivers/hv/vmbus_drv.c | 15 +++++++++++++++
drivers/pci/controller/pci-hyperv.c | 17 +++++++++++++----
include/linux/dma-map-ops.h | 9 +++++++++
4 files changed, 38 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-03-17 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 16:12 Michael Kelley [this message]
2022-03-17 16:12 ` [PATCH 1/4] ACPI: scan: Export acpi_get_dma_attr() Michael Kelley
2022-03-17 16:12 ` [PATCH 2/4] dma-mapping: Add wrapper function to set dma_coherent Michael Kelley
2022-03-17 16:12 ` [PATCH 3/4] Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device Michael Kelley
2022-03-17 16:12 ` [PATCH 4/4] PCI: hv: Propagate coherence from VMbus device to PCI device Michael Kelley
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=1647533563-2170-1-git-send-email-mikelley@microsoft.com \
--to=mikelley@microsoft.com \
--cc=bhelgass@google.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).