diff options
| author | Niklas Schnelle <schnelle@linux.ibm.com> | 2022-09-07 11:38:30 +0200 |
|---|---|---|
| committer | Vasily Gorbik <gor@linux.ibm.com> | 2022-09-14 16:46:00 +0200 |
| commit | 2187582c361fcd33a6ab5e9e6fef5b774c3b8cda (patch) | |
| tree | 416efbb4ecbc83199d7d54c594af12eea9ea17fb /arch/s390 | |
| parent | 50787755317ddf8c9bb3419a15b87c42237000cb (diff) | |
| download | linux-rpi-2187582c361fcd33a6ab5e9e6fef5b774c3b8cda.tar.gz linux-rpi-2187582c361fcd33a6ab5e9e6fef5b774c3b8cda.tar.bz2 linux-rpi-2187582c361fcd33a6ab5e9e6fef5b774c3b8cda.zip | |
s390/pci: convert high_memory to physical address
We use high_memory as a measure for amount of memory available in
determining the required minimum size of our IOVA space with the
assumption that one rarely maps more than the available memory for DMA.
In special cases like mapping significant amounts of memory more than
once this can still be tuned with the s390_iommu_apterture kernel
parameter. In this use case high_memory is treated as a physical
address. As high_memory is a virtual address however this means we need
to convert it using virt_to_phys() before use
Note that at the moment physical and virtual addresses are identical so
this mismatch does not currently cause trouble.
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'arch/s390')
| -rw-r--r-- | arch/s390/pci/pci_dma.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/pci/pci_dma.c b/arch/s390/pci/pci_dma.c index f46833a25526..227cf0a62800 100644 --- a/arch/s390/pci/pci_dma.c +++ b/arch/s390/pci/pci_dma.c @@ -666,7 +666,7 @@ static int __init dma_alloc_cpu_table_caches(void) int __init zpci_dma_init(void) { - s390_iommu_aperture = (u64)high_memory; + s390_iommu_aperture = (u64)virt_to_phys(high_memory); if (!s390_iommu_aperture_factor) s390_iommu_aperture = ULONG_MAX; else |