summaryrefslogtreecommitdiffstats
path: root/tools/virtio
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2018-04-12 09:33:30 +0200
committerChristoph Hellwig <hch@lst.de>2018-05-07 07:15:41 +0200
commit325ef1857fff8b2049322921e19421b6c5ad74e5 (patch)
treed4f0dc35d4e37e18c432e76292e3a453462dd02e /tools/virtio
parentab74cfebafa3b71caa1e82793032b4867dcf5ea6 (diff)
downloadlinux-325ef1857fff8b2049322921e19421b6c5ad74e5.tar.gz
linux-325ef1857fff8b2049322921e19421b6c5ad74e5.tar.bz2
linux-325ef1857fff8b2049322921e19421b6c5ad74e5.zip
PCI: remove PCI_DMA_BUS_IS_PHYS
This was used by the ide, scsi and networking code in the past to determine if they should bounce payloads. Now that the dma mapping always have to support dma to all physical memory (thanks to swiotlb for non-iommu systems) there is no need to this crude hack any more. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Palmer Dabbelt <palmer@sifive.com> (for riscv) Reviewed-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/virtio')
-rw-r--r--tools/virtio/linux/dma-mapping.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/tools/virtio/linux/dma-mapping.h b/tools/virtio/linux/dma-mapping.h
index 1571e24e9494..f91aeb5fe571 100644
--- a/tools/virtio/linux/dma-mapping.h
+++ b/tools/virtio/linux/dma-mapping.h
@@ -6,8 +6,6 @@
# error Virtio userspace code does not support CONFIG_HAS_DMA
#endif
-#define PCI_DMA_BUS_IS_PHYS 1
-
enum dma_data_direction {
DMA_BIDIRECTIONAL = 0,
DMA_TO_DEVICE = 1,