<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>150745b4 - dma-debug: remove DMA_API_DEBUG_SG</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#150745b4</link>
        <description>dma-debug: remove DMA_API_DEBUG_SGThe scatterlist validity checks are pretty simple and cheap, perform themunconditionally.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Tue, 15 Oct 2024 08:29:20 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>de6c85bf - dma-mapping: clearly mark DMA ops as an architecture feature</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#de6c85bf</link>
        <description>dma-mapping: clearly mark DMA ops as an architecture featureDMA ops are a helper for architectures and not for drivers to overridethe DMA implementation.Unfortunately driver authors keep ignoring this.  Make the fact moreclear by renaming the symbol to ARCH_HAS_DMA_OPS and having the two driversoverriding their dma_ops depend on that.  These drivers should probably bemarked broken, but we can give them a bit of a grace period for that.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt; # for IPU6Acked-by: Robin Murphy &lt;robin.murphy@arm.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 28 Aug 2024 06:02:47 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>b5c58b2f - dma-mapping: direct calls for dma-iommu</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#b5c58b2f</link>
        <description>dma-mapping: direct calls for dma-iommuDirectly call into dma-iommu just like we have been doing for dma-directfor a while.  This avoids the indirect call overhead for IOMMU ops andremoves the need to have DMA ops entirely for many common configurations.Signed-off-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;Signed-off-by: Leon Romanovsky &lt;leon@kernel.org&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 24 Jul 2024 18:04:49 +0000</pubDate>
        <dc:creator>Leon Romanovsky &lt;leonro@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>fe7514b1 - dma: compile-out DMA sync op calls when not used</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#fe7514b1</link>
        <description>dma: compile-out DMA sync op calls when not usedSome platforms do have DMA, but DMA there is always direct and coherent.Currently, even on such platforms DMA sync operations are compiled andcalled.Add a new hidden Kconfig symbol, DMA_NEED_SYNC, and set it only wheneither sync operations are needed or there is DMA ops or swiotlbor DMA debug is enabled. Compile global dma_sync_*() and dma_need_sync()only when it&apos;s set, otherwise provide empty inline stubs.The change allows for future optimizations of DMA sync calls dependingon runtime conditions.Signed-off-by: Alexander Lobakin &lt;aleksander.lobakin@intel.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Tue, 07 May 2024 11:20:20 +0000</pubDate>
        <dc:creator>Alexander Lobakin &lt;aleksander.lobakin@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>2c8ed1b9 - dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbol</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#2c8ed1b9</link>
        <description>dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbolInstead of using arch_dma_alloc if none of the generic coherentallocators are used, require the architectures to explicitly opt intoproviding it.  This will used to deal with the case of m68knommu andcoldfire where we can&apos;t do any coherent allocations whatsoever, andalso makes it clear that arch_dma_alloc is a last resort.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Reviewed-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Tested-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Thu, 05 Oct 2023 07:05:36 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>da323d46 - dma-direct: add dependencies to CONFIG_DMA_GLOBAL_POOL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#da323d46</link>
        <description>dma-direct: add dependencies to CONFIG_DMA_GLOBAL_POOLCONFIG_DMA_GLOBAL_POOL can&apos;t be combined with other DMA coherentallocators.  Add dependencies to Kconfig to document this, and makekconfig complain about unmet dependencies if someone tries.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Reviewed-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;Reviewed-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Tested-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Thu, 05 Oct 2023 07:06:55 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>2dcdf8c1 - dma-contiguous: fix the Kconfig entry for CONFIG_DMA_NUMA_CMA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#2dcdf8c1</link>
        <description>dma-contiguous: fix the Kconfig entry for CONFIG_DMA_NUMA_CMAIt makes no sense to expose CONFIG_DMA_NUMA_CMA if CONFIG_NUMA is notenabled, and random config options shouldn&apos;t be default unless thereis a good reason.  Replace the default NUMA with a depends on to fix bothissues.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;roin.murphy@arm.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 30 Aug 2023 09:25:25 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>62708b2b - swiotlb: add a flag whether SWIOTLB is allowed to grow</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#62708b2b</link>
        <description>swiotlb: add a flag whether SWIOTLB is allowed to growAdd a config option (CONFIG_SWIOTLB_DYNAMIC) to enable or disable dynamicallocation of additional bounce buffers.If this option is set, mark the default SWIOTLB as able to grow andrestricted DMA pools as unable.However, if the address of the default memory pool is explicitly queried,make the default SWIOTLB also unable to grow. This is currently used to setup PCI BAR movable regions on some Octeon MIPS boards which may not be ableto use a SWIOTLB pool elsewhere in physical memory. See octeon_pci_setup()for more details.If a remap function is specified, it must be also called on any dynamicallyallocated pools, but there are some issues:- The remap function may block, so it should not be called from an atomic  context.- There is no corresponding unremap() function if the memory pool is  freed.- The only in-tree implementation (xen_swiotlb_fixup) requires that the  number of slots in the memory pool is a multiple of SWIOTLB_SEGSIZE.Keep it simple for now and disable growing the SWIOTLB if a remap functionwas specified.Signed-off-by: Petr Tesarik &lt;petr.tesarik.ext@huawei.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Tue, 01 Aug 2023 06:24:00 +0000</pubDate>
        <dc:creator>Petr Tesarik &lt;petr.tesarik.ext@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>bf29bfaa - dma-contiguous: support numa CMA for specified node</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#bf29bfaa</link>
        <description>dma-contiguous: support numa CMA for specified nodeThe kernel parameter &apos;cma_pernuma=&apos; only supports reserving the samesize of CMA area for each node. We need to reserve different sizes ofCMA area for specified nodes if these devices belong to different nodes.Adding another kernel parameter &apos;numa_cma=&apos; to reserve CMA area forthe specified node. If we want to use one of these parameters, we need toenable DMA_NUMA_CMA.At the same time, print the node id in cma_declare_contiguous_nid() ifCONFIG_NUMA is enabled.Signed-off-by: Yajun Deng &lt;yajun.deng@linux.dev&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 12 Jul 2023 07:47:58 +0000</pubDate>
        <dc:creator>Yajun Deng &lt;yajun.deng@linux.dev&gt;</dc:creator>
    </item>
<item>
        <title>22e4a348 - dma-contiguous: support per-numa CMA for all architectures</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#22e4a348</link>
        <description>dma-contiguous: support per-numa CMA for all architecturesIn the commit b7176c261cdb (&quot;dma-contiguous: provide the ability toreserve per-numa CMA&quot;), Barry adds DMA_PERNUMA_CMA for ARM64.But this feature is architecture independent, so support per-numa CMAfor all architectures, and enable it by default if NUMA.Signed-off-by: Yajun Deng &lt;yajun.deng@linux.dev&gt;Tested-by: Yicong Yang &lt;yangyicong@hisilicon.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Fri, 12 May 2023 09:42:10 +0000</pubDate>
        <dc:creator>Yajun Deng &lt;yajun.deng@linux.dev&gt;</dc:creator>
    </item>
<item>
        <title>370645f4 - dma-mapping: force bouncing if the kmalloc() size is not cache-line-aligned</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#370645f4</link>
        <description>dma-mapping: force bouncing if the kmalloc() size is not cache-line-alignedFor direct DMA, if the size is small enough to have originated from akmalloc() cache below ARCH_DMA_MINALIGN, check its alignment againstdma_get_cache_alignment() and bounce if necessary.  For larger sizes, itis the responsibility of the DMA API caller to ensure proper alignment.At this point, the kmalloc() caches are properly aligned but this willchange in a subsequent patch.Architectures can opt in by selecting DMA_BOUNCE_UNALIGNED_KMALLOC.Link: https://lkml.kernel.org/r/20230612153201.554742-15-catalin.marinas@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Tested-by: Isaac J. Manjarres &lt;isaacmanjarres@google.com&gt;Cc: Alasdair Kergon &lt;agk@redhat.com&gt;Cc: Ard Biesheuvel &lt;ardb@kernel.org&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Cc: Jerry Snitselaar &lt;jsnitsel@redhat.com&gt;Cc: Joerg Roedel &lt;joro@8bytes.org&gt;Cc: Jonathan Cameron &lt;jic23@kernel.org&gt;Cc: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Cc: Lars-Peter Clausen &lt;lars@metafoo.de&gt;Cc: Logan Gunthorpe &lt;logang@deltatee.com&gt;Cc: Marc Zyngier &lt;maz@kernel.org&gt;Cc: Mark Brown &lt;broonie@kernel.org&gt;Cc: Mike Snitzer &lt;snitzer@kernel.org&gt;Cc: &quot;Rafael J. Wysocki&quot; &lt;rafael@kernel.org&gt;Cc: Saravana Kannan &lt;saravanak@google.com&gt;Cc: Vlastimil Babka &lt;vbabka@suse.cz&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Mon, 12 Jun 2023 15:31:58 +0000</pubDate>
        <dc:creator>Catalin Marinas &lt;catalin.marinas@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>af2880ec - scatterlist: add dedicated config for DMA flags</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#af2880ec</link>
        <description>scatterlist: add dedicated config for DMA flagsThe DMA flags field will be useful for users beyond PCI P2P, so upgrade toits own dedicated config option.[catalin.marinas@arm.com: use #ifdef CONFIG_NEED_SG_DMA_FLAGS in scatterlist.h][catalin.marinas@arm.com: update PCI_P2PDMA dma_flags comment in scatterlist.h]Link: https://lkml.kernel.org/r/20230612153201.554742-13-catalin.marinas@arm.comSigned-off-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Tested-by: Isaac J. Manjarres &lt;isaacmanjarres@google.com&gt;Cc: Alasdair Kergon &lt;agk@redhat.com&gt;Cc: Ard Biesheuvel &lt;ardb@kernel.org&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Cc: Jerry Snitselaar &lt;jsnitsel@redhat.com&gt;Cc: Joerg Roedel &lt;joro@8bytes.org&gt;Cc: Jonathan Cameron &lt;jic23@kernel.org&gt;Cc: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Cc: Lars-Peter Clausen &lt;lars@metafoo.de&gt;Cc: Logan Gunthorpe &lt;logang@deltatee.com&gt;Cc: Marc Zyngier &lt;maz@kernel.org&gt;Cc: Mark Brown &lt;broonie@kernel.org&gt;Cc: Mike Snitzer &lt;snitzer@kernel.org&gt;Cc: &quot;Rafael J. Wysocki&quot; &lt;rafael@kernel.org&gt;Cc: Saravana Kannan &lt;saravanak@google.com&gt;Cc: Vlastimil Babka &lt;vbabka@suse.cz&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Mon, 12 Jun 2023 15:31:56 +0000</pubDate>
        <dc:creator>Robin Murphy &lt;robin.murphy@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>4d3af20e - dma-mapping: fix a Kconfig typo</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#4d3af20e</link>
        <description>dma-mapping: fix a Kconfig typo&apos;thing&apos; -&gt; &apos;think&apos;Signed-off-by: Sui Jingfeng &lt;suijingfeng@loongson.cn&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Sun, 04 Jun 2023 13:50:54 +0000</pubDate>
        <dc:creator>Sui Jingfeng &lt;suijingfeng@loongson.cn&gt;</dc:creator>
    </item>
<item>
        <title>1d3f56b2 - dma-mapping: provide CONFIG_ARCH_DMA_DEFAULT_COHERENT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#1d3f56b2</link>
        <description>dma-mapping: provide CONFIG_ARCH_DMA_DEFAULT_COHERENTProvide a kconfig option to allow arches to manipulate defaultvalue of dma_default_coherent in Kconfig.Signed-off-by: Jiaxun Yang &lt;jiaxun.yang@flygoat.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Sat, 01 Apr 2023 09:15:30 +0000</pubDate>
        <dc:creator>Jiaxun Yang &lt;jiaxun.yang@flygoat.com&gt;</dc:creator>
    </item>
<item>
        <title>f5ff79fd - dma-mapping: remove CONFIG_DMA_REMAP</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#f5ff79fd</link>
        <description>dma-mapping: remove CONFIG_DMA_REMAPCONFIG_DMA_REMAP is used to build a few helpers around the corevmalloc code, and to use them in case there is a highmem page indma-direct, and to make dma coherent allocations be able to usenon-contiguous pages allocations for DMA allocations in the dma-iommulayer.Right now it needs to be explicitly selected by architectures, andis only done so by architectures that require remapping to dealwith devices that are not DMA coherent.  Make it unconditional forbuilds with CONFIG_MMU as it is very little extra code, but makesit much more likely that large DMA allocations succeed on x86.This fixes hot plugging a NVMe thunderbolt SSD for me, which triesto allocate a 1MB buffer that is otherwise hard to obtain due tomemory fragmentation on a heavily used laptop.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Sat, 26 Feb 2022 15:40:21 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>f3c4b134 - swiotlb: use depends on for DMA_RESTRICTED_POOL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#f3c4b134</link>
        <description>swiotlb: use depends on for DMA_RESTRICTED_POOLUse depends on instead of select for DMA_RESTRICTED_POOL; otherwise itwill make SWIOTLB user configurable and cause compile errors for somearch (e.g. mips).Fixes: 0b84e4f8b793 (&quot;swiotlb: Add restricted DMA pool initialization&quot;)Acked-by: Will Deacon &lt;will@kernel.org&gt;Reported-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Signed-off-by: Claire Chang &lt;tientzu@chromium.org&gt;Signed-off-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Fri, 27 Aug 2021 03:48:02 +0000</pubDate>
        <dc:creator>Claire Chang &lt;tientzu@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>faf4ef82 - dma-direct: add support for dma_coherent_default_memory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#faf4ef82</link>
        <description>dma-direct: add support for dma_coherent_default_memoryAdd an option to allocate uncached memory for dma_alloc_coherent fromthe global dma_coherent_default_memory.  This will allow to movearm-nommu (and eventually other platforms) to use generic code forallocating uncached memory from a pre-populated pool.Note that this is a different pool from the one that platforms thatcan remap at runtime use for GFP_ATOMIC allocations for now, althoughthere might be opportunities to eventually end up with a common codebasefor the two use cases.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Tested-by: Dillon Min &lt;dillon.minfei@gmail.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 23 Jun 2021 12:21:16 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>0b84e4f8 - swiotlb: Add restricted DMA pool initialization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#0b84e4f8</link>
        <description>swiotlb: Add restricted DMA pool initializationAdd the initialization function to create restricted DMA pools frommatching reserved-memory nodes.Regardless of swiotlb setting, the restricted DMA pool is preferred ifavailable.The restricted DMA pools provide a basic level of protection against theDMA overwriting buffer contents at unexpected times. However, to protectagainst general data leakage and system memory corruption, the systemneeds to provide a way to lock down the memory access, e.g., MPU.Signed-off-by: Claire Chang &lt;tientzu@chromium.org&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Tested-by: Stefano Stabellini &lt;sstabellini@kernel.org&gt;Tested-by: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Sat, 19 Jun 2021 03:40:41 +0000</pubDate>
        <dc:creator>Claire Chang &lt;tientzu@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>6d4e9a8e - driver core: lift dma_default_coherent into common code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#6d4e9a8e</link>
        <description>driver core: lift dma_default_coherent into common codeLift the dma_default_coherent variable from the mips architecture codeto the driver core.  This allows an architecture to sdefault all deviceto be DMA coherent at run time, even if the kernel is build with supportfor DMA noncoherent device.  By allowing device_initialize to set the-&gt;dma_coherent field to this default the amount of arch hooks requiredfor this behavior can be greatly reduced.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Wed, 10 Feb 2021 09:56:39 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>65789daa - dma-mapping: add benchmark support for streaming DMA APIs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/kernel/dma/Kconfig#65789daa</link>
        <description>dma-mapping: add benchmark support for streaming DMA APIsNowadays, there are increasing requirements to benchmark the performanceof dma_map and dma_unmap particually while the device is attached to anIOMMU.This patch enables the support. Users can run specified number of threadsto do dma_map_page and dma_unmap_page on a specific NUMA node with thespecified duration. Then dma_map_benchmark will calculate the averagelatency for map and unmap.A difficulity for this benchmark is that dma_map/unmap APIs must run ona particular device. Each device might have different backend of IOMMU ornon-IOMMU.So we use the driver_override to bind dma_map_benchmark to a particualdevice by:For platform devices:echo dma_map_benchmark &gt; /sys/bus/platform/devices/xxx/driver_overrideecho xxx &gt; /sys/bus/platform/drivers/xxx/unbindecho xxx &gt; /sys/bus/platform/drivers/dma_map_benchmark/bindFor PCI devices:echo dma_map_benchmark &gt; /sys/bus/pci/devices/0000:00:01.0/driver_overrideecho 0000:00:01.0 &gt; /sys/bus/pci/drivers/xxx/unbindecho 0000:00:01.0 &gt; /sys/bus/pci/drivers/dma_map_benchmark/bindCc: Will Deacon &lt;will@kernel.org&gt;Cc: Shuah Khan &lt;shuah@kernel.org&gt;Cc: Christoph Hellwig &lt;hch@lst.de&gt;Cc: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;Cc: Robin Murphy &lt;robin.murphy@arm.com&gt;Signed-off-by: Barry Song &lt;song.bao.hua@hisilicon.com&gt;[hch: folded in two fixes from Colin Ian King &lt;colin.king@canonical.com&gt;]Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/kernel/dma/Kconfig</description>
        <pubDate>Mon, 16 Nov 2020 06:08:47 +0000</pubDate>
        <dc:creator>Barry Song &lt;song.bao.hua@hisilicon.com&gt;</dc:creator>
    </item>
</channel>
</rss>
