diff options
author | 2018-12-10 14:00:31 +0000 | |
---|---|---|
committer | 2018-12-11 14:32:12 +0100 | |
commit | a8a4c98fc9ac84ee9e068fbb16210d2ab8cfefe0 (patch) | |
tree | 216128ca9be3b97e771a4f1b0f31aae1acee9a2a /tools/perf/scripts/python/export-to-postgresql.py | |
parent | dma-debug: Make leak-like behaviour apparent (diff) | |
download | wireguard-linux-a8a4c98fc9ac84ee9e068fbb16210d2ab8cfefe0.tar.xz wireguard-linux-a8a4c98fc9ac84ee9e068fbb16210d2ab8cfefe0.zip |
x86/dma/amd-gart: Stop resizing dma_debug_entry pool
dma-debug is now capable of adding new entries to its pool on-demand if
the initial preallocation was insufficient, so the IOMMU_LEAK logic no
longer needs to explicitly change the pool size. This does lose it the
ability to save a couple of megabytes of RAM by reducing the pool size
below its default, but it seems unlikely that that is a realistic
concern these days (or indeed that anyone is actively debugging AGP
drivers' DMA usage any more). Getting rid of dma_debug_resize_entries()
will make room for further streamlining in the dma-debug code itself.
Removing the call reveals quite a lot of cruft which has been useless
for nearly a decade since commit 19c1a6f5764d ("x86 gart: reimplement
IOMMU_LEAK feature by using DMA_API_DEBUG"), including the entire
'iommu=leak' parameter, which controlled nothing except whether
dma_debug_resize_entries() was called or not.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Qian Cai <cai@lca.pw>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions