<?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>140f5ded - iommu/vt-d: Move IOMMU_IOPF into INTEL_IOMMU</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#140f5ded</link>
        <description>iommu/vt-d: Move IOMMU_IOPF into INTEL_IOMMUMove IOMMU_IOPF from under INTEL_IOMMU_SVM into INTEL_IOMMU. Thiscertifies that the core intel iommu utilizes the IOPF libraryfunctions, independent of the INTEL_IOMMU_SVM config.Signed-off-by: Joel Granados &lt;joel.granados@kernel.org&gt;Link: https://lore.kernel.org/r/20241015-jag-iopfv8-v4-3-b696ca89ba29@kernel.orgSigned-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Signed-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Mon, 04 Nov 2024 01:40:36 +0000</pubDate>
        <dc:creator>Joel Granados &lt;joel.granados@kernel.org&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/drivers/iommu/intel/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/drivers/iommu/intel/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>4b8d18c0 - iommu/vt-d: Remove INTEL_IOMMU_BROKEN_GFX_WA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#4b8d18c0</link>
        <description>iommu/vt-d: Remove INTEL_IOMMU_BROKEN_GFX_WACommit 62edf5dc4a524 (&quot;intel-iommu: Restore DMAR_BROKEN_GFX_WA option forbroken graphics drivers&quot;) was introduced 24 years ago as a temporaryworkaround for graphics drivers that used physical addresses for DMA andavoided DMA APIs. This workaround was disabled by default.As 24 years have passed, it is expected that graphics driver developershave migrated their drivers to use kernel DMA APIs. Therefore, thisworkaround is no longer required and could been removed.The Intel iommu driver also provides a &quot;igfx_off&quot; option to turn offthe DMA translation for the graphic dedicated IOMMU. Hence, there isreally no good reason to keep this config option.Suggested-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Reviewed-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Link: https://lore.kernel.org/r/20240130060823.57990-1-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 27 Feb 2024 02:14:34 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>cd14b018 - treewide: replace or remove redundant def_bool in Kconfig files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#cd14b018</link>
        <description>treewide: replace or remove redundant def_bool in Kconfig files&apos;def_bool X&apos; is a shorthand for &apos;bool&apos; plus &apos;default X&apos;.&apos;def_bool&apos; is redundant where &apos;bool&apos; is already present, so &apos;def_bool X&apos;can be replaced with &apos;default X&apos;, or removed if X is &apos;n&apos;.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Sun, 11 Feb 2024 12:48:08 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>17c51a0e - iommu: Separate SVA and IOPF</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#17c51a0e</link>
        <description>iommu: Separate SVA and IOPFAdd CONFIG_IOMMU_IOPF for page fault handling framework and select itfrom its real consumer. Move iopf function declaration from iommu-sva.hto iommu.h and remove iommu-sva.h as it&apos;s empty now.Consolidate all SVA related code into iommu-sva.c:- Move iommu_sva_domain_alloc() from iommu.c to iommu-sva.c.- Move sva iopf handling code from io-pgfault.c to iommu-sva.c.Consolidate iommu_report_device_fault() and iommu_page_response() intoio-pgfault.c.Export iopf_free_group() and iopf_group_response() for iopf handlersimplemented in modules. Some functions are renamed with more meaningfulnames. No other intentional functionality changes.Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Reviewed-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Reviewed-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Tested-by: Yan Zhao &lt;yan.y.zhao@intel.com&gt;Tested-by: Longfang Liu &lt;liulongfang@huawei.com&gt;Link: https://lore.kernel.org/r/20240212012227.119381-11-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Mon, 12 Feb 2024 01:22:21 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f35f22cc - iommu/vt-d: Access/Dirty bit support for SS domains</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#f35f22cc</link>
        <description>iommu/vt-d: Access/Dirty bit support for SS domainsIOMMU advertises Access/Dirty bits for second-stage page table if theextended capability DMAR register reports it (ECAP, mnemonic ECAP.SSADS).The first stage table is compatible with CPU page table thus A/D bits areimplicitly supported. Relevant Intel IOMMU SDM ref for first stage table&quot;3.6.2 Accessed, Extended Accessed, and Dirty Flags&quot; and second stage table&quot;3.7.2 Accessed and Dirty Flags&quot;.First stage page table is enabled by default so it&apos;s allowed to set dirtytracking and no control bits needed, it just returns 0. To use SSADS, setbit 9 (SSADE) in the scalable-mode PASID table entry and flush the IOTLBvia pasid_flush_caches() following the manual. Relevant SDM refs:&quot;3.7.2 Accessed and Dirty Flags&quot;&quot;6.5.3.3 Guidance to Software for Invalidations, Table 23. Guidance to Software for Invalidations&quot;PTE dirty bit is located in bit 9 and it&apos;s cached in the IOTLB so flushIOTLB to make sure IOMMU attempts to set the dirty bit again. Note thatiommu_dirty_bitmap_record() will add the IOVA to iotlb_gather and thus thecaller of the iommu op will flush the IOTLB. Relevant manuals over thehardware translation is chapter 6 with some special mention to:&quot;6.2.3.1 Scalable-Mode PASID-Table Entry Programming Considerations&quot;&quot;6.2.4 IOTLB&quot;Select IOMMUFD_DRIVER only if IOMMUFD is enabled, given that IOMMU dirtytracking requires IOMMUFD.Link: https://lore.kernel.org/r/20231024135109.73787-13-joao.m.martins@oracle.comSigned-off-by: Joao Martins &lt;joao.m.martins@oracle.com&gt;Reviewed-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Reviewed-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 24 Oct 2023 13:51:03 +0000</pubDate>
        <dc:creator>Joao Martins &lt;joao.m.martins@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>cf8e8658 - arch: Remove Itanium (IA-64) architecture</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#cf8e8658</link>
        <description>arch: Remove Itanium (IA-64) architectureThe Itanium architecture is obsolete, and an informal survey [0] revealsthat any residual use of Itanium hardware in production is mostly HP-UXor OpenVMS based. The use of Linux on Itanium appears to be limited toenthusiasts that occasionally boot a fresh Linux kernel to see whetherthings are still working as intended, and perhaps to churn out somedistro packages that are rarely used in practice.None of the original companies behind Itanium still produce or supportany hardware or software for the architecture, and it is listed as&apos;Orphaned&apos; in the MAINTAINERS file, as apparently, none of the engineersthat contributed on behalf of those companies (nor anyone else, for thatmatter) have been willing to support or maintain the architectureupstream or even be responsible for applying the odd fix. The Intelfirmware team removed all IA-64 support from the Tianocore/EDK2reference implementation of EFI in 2018. (Itanium is the originalarchitecture for which EFI was developed, and the way Linux supports itdeviates significantly from other architectures.) Some distros, such asDebian and Gentoo, still maintain [unofficial] ia64 ports, but many havedropped support years ago.While the argument is being made [1] that there is a &apos;for the commongood&apos; angle to being able to build and run existing projects such as theGrid Community Toolkit [2] on Itanium for interoperability testing, thefact remains that none of those projects are known to be deployed onLinux/ia64, and very few people actually have access to such a system inthe first place. Even if there were ways imaginable in which Linux/ia64could be put to good use today, what matters is whether anyone isactually doing that, and this does not appear to be the case.There are no emulators widely available, and so boot testing Itanium isgenerally infeasible for ordinary contributors. GCC still supports IA-64but its compile farm [3] no longer has any IA-64 machines. GLIBC wouldlike to get rid of IA-64 [4] too because it would permit some overduecode cleanups. In summary, the benefits to the ecosystem of having IA-64be part of it are mostly theoretical, whereas the maintenance overheadof keeping it supported is real.So let&apos;s rip off the band aid, and remove the IA-64 arch code entirely.This follows the timeline proposed by the Debian/ia64 maintainer [5],which removes support in a controlled manner, leaving IA-64 in a knowngood state in the most recent LTS release. Other projects will followonce the kernel support is removed.[0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/[1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/[2] https://gridcf.org/gct-docs/latest/index.html[3] https://cfarm.tetaneutral.net/machines/list/[4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/[5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/Acked-by: Tony Luck &lt;tony.luck@intel.com&gt;Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 20 Oct 2022 13:54:33 +0000</pubDate>
        <dc:creator>Ard Biesheuvel &lt;ardb@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>a6a5006d - iommu/vt-d: Retrieve IOMMU perfmon capability information</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#a6a5006d</link>
        <description>iommu/vt-d: Retrieve IOMMU perfmon capability informationThe performance monitoring infrastructure, perfmon, is to supportcollection of information about key events occurring during operation ofthe remapping hardware, to aid performance tuning and debug. Eachremapping hardware unit has capability registers that indicate supportfor performance monitoring features and enumerate the capabilities.Add alloc_iommu_pmu() to retrieve IOMMU perfmon capability informationfor each iommu unit. The information is stored in the iommu-&gt;pmu datastructure. Capability registers are read-only, so it&apos;s safe to prefetchand store them in the pmu structure. This could avoid unnecessary VMEXITwhen this code is running in the virtualization environment.Add free_iommu_pmu() to free the saved capability information whenfreeing the iommu unit.Add a kernel config option for the IOMMU perfmon feature. Unless a userexplicitly uses the perf tool to monitor the IOMMU perfmon event, thereisn&apos;t any impact for the existing IOMMU. Enable it by default.Signed-off-by: Kan Liang &lt;kan.liang@linux.intel.com&gt;Link: https://lore.kernel.org/r/20230128200428.1459118-3-kan.liang@linux.intel.comSigned-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Signed-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 31 Jan 2023 07:37:35 +0000</pubDate>
        <dc:creator>Kan Liang &lt;kan.liang@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0faa19a1 - iommu/vt-d: Decouple PASID &amp; PRI enabling from SVA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#0faa19a1</link>
        <description>iommu/vt-d: Decouple PASID &amp; PRI enabling from SVAPreviously the PCI PASID and PRI capabilities are enabled in the path ofiommu device probe only if INTEL_IOMMU_SVM is configured and the devicesupports ATS. As we&apos;ve already decoupled the I/O page fault handler fromSVA, we could also decouple PASID and PRI enabling from it to make roomfor growth of new features like kernel DMA with PASID, SIOV and nestedtranslation.At the same time, the iommu_enable_dev_iotlb() helper is also called iniommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) path. It&apos;s unnecessaryand duplicate. This cleanups this helper to make the code neat.Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Reviewed-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Link: https://lore.kernel.org/r/20220915085814.2261409-1-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Mon, 26 Sep 2022 13:15:25 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>de9f8a91 - iommu/dma: Clean up Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#de9f8a91</link>
        <description>iommu/dma: Clean up KconfigAlthough iommu-dma is a per-architecture chonce, that is currentlyimplemented in a rather haphazard way. Selecting from the arch Kconfigwas the original logical approach, but is complicated by having tomanage dependencies; conversely, selecting from drivers ends up hidingthe architecture dependency *too* well. Instead, let&apos;s just have itenable itself automatically when IOMMU API support is enabled for therelevant architectures. It can&apos;t get much clearer than that.Signed-off-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Link: https://lore.kernel.org/r/2e33c8bc2b1bb478157b7964bfed976cb7466139.1660668998.git.robin.murphy@arm.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 16 Aug 2022 17:28:03 +0000</pubDate>
        <dc:creator>Robin Murphy &lt;robin.murphy@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>7ba56472 - iommu/sva: Rename CONFIG_IOMMU_SVA_LIB to CONFIG_IOMMU_SVA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#7ba56472</link>
        <description>iommu/sva: Rename CONFIG_IOMMU_SVA_LIB to CONFIG_IOMMU_SVAThis CONFIG option originally only referred to the SharedVirtual Address (SVA) library. But it is now also used fornon-library portions of code.Drop the &quot;_LIB&quot; suffix so that there is just one configurationoption for all code relating to SVA.Signed-off-by: Fenghua Yu &lt;fenghua.yu@intel.com&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;Reviewed-by: Tony Luck &lt;tony.luck@intel.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Reviewed-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20220207230254.3342514-2-fenghua.yu@intel.com

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Mon, 07 Feb 2022 23:02:44 +0000</pubDate>
        <dc:creator>Fenghua Yu &lt;fenghua.yu@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>914ff771 - iommu/vt-d: Dump DMAR translation structure when DMA fault occurs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#914ff771</link>
        <description>iommu/vt-d: Dump DMAR translation structure when DMA fault occursWhen the dmar translation fault happens, the kernel prints a single linefault reason with corresponding hexadecimal code defined in the Intel VT-dspecification.Currently, when user wants to debug the translation fault in detail,debugfs is used for dumping the dmar_translation_struct, which is notavailable when the kernel failed to boot.Dump the DMAR translation structure, pagewalk the IO page table and printthe page table entry when the fault happens.This takes effect only when CONFIG_DMAR_DEBUG is enabled.Signed-off-by: Kyung Min Park &lt;kyung.min.park@intel.com&gt;Link: https://lore.kernel.org/r/20210815203845.31287-1-kyung.min.park@intel.comSigned-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20211014053839.727419-3-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 14 Oct 2021 05:38:32 +0000</pubDate>
        <dc:creator>Kyung Min Park &lt;kyung.min.park@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>792fb43c - iommu/vt-d: Enable Intel IOMMU scalable mode by default</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#792fb43c</link>
        <description>iommu/vt-d: Enable Intel IOMMU scalable mode by defaultThe commit 8950dcd83ae7d (&quot;iommu/vt-d: Leave scalable mode default off&quot;)leaves the scalable mode default off and end users could turn it on with&quot;intel_iommu=sm_on&quot;. Using the Intel IOMMU scalable mode for kernel DMA,user-level device access and Shared Virtual Address have been enabled.This enables the scalable mode by default if the hardware advertises thesupport and adds kernel options of &quot;intel_iommu=sm_on/sm_off&quot; for endusers to configure it through the kernel parameters.Suggested-by: Ashok Raj &lt;ashok.raj@intel.com&gt;Suggested-by: Sanjay Kumar &lt;sanjay.k.kumar@intel.com&gt;Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Cc: Kevin Tian &lt;kevin.tian@intel.com&gt;Link: https://lore.kernel.org/r/20210720013856.4143880-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210818134852.1847070-5-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Wed, 18 Aug 2021 13:48:47 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>01dac2d9 - iommu/vt-d: Refactor Kconfig a bit</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#01dac2d9</link>
        <description>iommu/vt-d: Refactor Kconfig a bitPut all sub-options inside a &quot;if INTEL_IOMMU&quot; so that they don&apos;t need toalways depend on INTEL_IOMMU. Use IS_ENABLED() instead of #ifdef as well.Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20210720013856.4143880-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210818134852.1847070-4-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Wed, 18 Aug 2021 13:48:46 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>456bb0b9 - iommu/vt-d: Expose latency monitor data through debugfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#456bb0b9</link>
        <description>iommu/vt-d: Expose latency monitor data through debugfsA debugfs interface /sys/kernel/debug/iommu/intel/dmar_perf_latency iscreated to control and show counts of execution time ranges for varioustypes per DMAR. The interface may help debug any potential performanceissue.By default, the interface is disabled.Possible write value of /sys/kernel/debug/iommu/intel/dmar_perf_latency  0 - disable sampling all latency data  1 - enable sampling IOTLB invalidation latency data  2 - enable sampling devTLB invalidation latency data  3 - enable sampling intr entry cache invalidation latency data  4 - enable sampling prq handling latency dataRead /sys/kernel/debug/iommu/intel/dmar_perf_latency gives a snapshotof sampling result of all enabled monitors.Signed-off-by: Fenghua Yu &lt;fenghua.yu@intel.com&gt;Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20210520031531.712333-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210610020115.1637656-15-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 10 Jun 2021 02:01:06 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>55ee5e67 - iommu/vt-d: Add common code for dmar latency performance monitors</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#55ee5e67</link>
        <description>iommu/vt-d: Add common code for dmar latency performance monitorsThe execution time of some operations is very performance critical, suchas cache invalidation and PRQ processing time. This adds some common codeto monitor the execution time range of those operations. The interfacesinclude enabling/disabling, checking status, updating sampling data andproviding a common string format for users.Signed-off-by: Fenghua Yu &lt;fenghua.yu@intel.com&gt;Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20210520031531.712333-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210610020115.1637656-14-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 10 Jun 2021 02:01:05 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>40483774 - iommu/vt-d: Use iommu_sva_alloc(free)_pasid() helpers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#40483774</link>
        <description>iommu/vt-d: Use iommu_sva_alloc(free)_pasid() helpersAlign the pasid alloc/free code with the generic helpers defined in theiommu core. This also refactored the SVA binding code to improve thereadability.Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20210520031531.712333-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210610020115.1637656-8-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 10 Jun 2021 02:00:59 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>879fcc6b - iommu/vt-d: Select PCI_ATS explicitly</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#879fcc6b</link>
        <description>iommu/vt-d: Select PCI_ATS explicitlyThe Intel VT-d implementation supports device TLB management. SelectPCI_ATS explicitly so that the pci_ats helpers are always available.Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Acked-by: Will Deacon &lt;will@kernel.org&gt;Link: https://lore.kernel.org/r/20210512065313.3441309-1-baolu.lu@linux.intel.comLink: https://lore.kernel.org/r/20210610020115.1637656-5-baolu.lu@linux.intel.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Thu, 10 Jun 2021 02:00:56 +0000</pubDate>
        <dc:creator>Lu Baolu &lt;baolu.lu@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c588072b - iommu/vt-d: Convert intel iommu driver to the iommu ops</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#c588072b</link>
        <description>iommu/vt-d: Convert intel iommu driver to the iommu opsConvert the intel iommu driver to the dma-iommu api. Remove the iovahandling and reserve region code from the intel iommu driver.Signed-off-by: Tom Murphy &lt;murphyt7@tcd.ie&gt;Signed-off-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Tested-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Link: https://lore.kernel.org/r/20201124082057.2614359-7-baolu.lu@linux.intel.comSigned-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 24 Nov 2020 08:20:56 +0000</pubDate>
        <dc:creator>Tom Murphy &lt;murphyt7@tcd.ie&gt;</dc:creator>
    </item>
<item>
        <title>ab65ba57 - iommu/vt-d: Move Kconfig and Makefile bits down into intel directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iommu/intel/Kconfig#ab65ba57</link>
        <description>iommu/vt-d: Move Kconfig and Makefile bits down into intel directoryMove Intel Kconfig and Makefile bits down into intel directorywith the rest of the Intel specific files.Signed-off-by: Jerry Snitselaar &lt;jsnitsel@redhat.com&gt;Reviewed-by: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Cc: Joerg Roedel &lt;joro@8bytes.org&gt;Cc: Lu Baolu &lt;baolu.lu@linux.intel.com&gt;Link: https://lore.kernel.org/r/20200630200636.48600-2-jsnitsel@redhat.comSigned-off-by: Joerg Roedel &lt;jroedel@suse.de&gt;

            List of files:
            /linux-6.15/drivers/iommu/intel/Kconfig</description>
        <pubDate>Tue, 30 Jun 2020 20:06:35 +0000</pubDate>
        <dc:creator>Jerry Snitselaar &lt;jsnitsel@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
