[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190611175825.572-1-f.fainelli@gmail.com>
Date: Tue, 11 Jun 2019 10:58:23 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: linux-kernel@...r.kernel.org
Cc: bcm-kernel-feedback-list@...adcom.com,
Florian Fainelli <f.fainelli@...il.com>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
"David S. Miller" <davem@...emloft.net>,
iommu@...ts.linux-foundation.org (open list:DMA MAPPING HELPERS),
netdev@...r.kernel.org (open list:NETWORKING [GENERAL])
Subject: [PATCH 0/2] swiotlb: Cleanup and consistency fix
Hi Christoph,
Still with my contrived memory layout where there is no physical memory
the kernel can use below 4GB, it was possible to fail swiotlb_init(),
but still not hit swiotlb_map_single() since all peripherals have a
DMA_BIT_MASK() that is within the remaining addressable physical memory.
The second path could be backported to stable, but for the same reasons
as the one we had just discussed before, this requires a very contrived
test case that is not necessarily realistic or would warrant a stable
backport IMHO.
Thanks!
Florian Fainelli (2):
swiotlb: Group identical cleanup in swiotlb_cleanup()
swiotlb: Return consistent SWIOTLB segments/nr_tbl
kernel/dma/swiotlb.c | 26 ++++++++++++++------------
1 file changed, 14 insertions(+), 12 deletions(-)
--
2.17.1
Powered by blists - more mailing lists