<?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>adc3e82d - ACPI: NUMA: change the ACPI_NUMA to a hidden option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/numa/Kconfig#adc3e82d</link>
        <description>ACPI: NUMA: change the ACPI_NUMA to a hidden optionx86/arm64/loongarch would select ACPI_NUMA by default and riscvwould do the same thing, so change it to a hidden option and theselect statements except for the X86_64_ACPI_NUMA can also go away.Suggested-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Suggested-by: Sunil V L &lt;sunilvl@ventanamicro.com&gt;Signed-off-by: Haibo Xu &lt;haibo1.xu@intel.com&gt;Reviewed-by: Sunil V L &lt;sunilvl@ventanamicro.com&gt;Acked-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;Acked-by: Will Deacon &lt;will@kernel.org&gt;Reviewed-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;Link: https://lore.kernel.org/r/f1f96377b8ecd6e3183f28abf5c9ac21cb9855ea.1718268003.git.haibo1.xu@intel.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/numa/Kconfig</description>
        <pubDate>Thu, 13 Jun 2024 08:54:35 +0000</pubDate>
        <dc:creator>Haibo Xu &lt;haibo1.xu@intel.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/acpi/numa/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/acpi/numa/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>b1121e2a - ACPI: Add LoongArch support for ACPI_PROCESSOR/ACPI_NUMA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/numa/Kconfig#b1121e2a</link>
        <description>ACPI: Add LoongArch support for ACPI_PROCESSOR/ACPI_NUMAWe are preparing to add new Loongson (based on LoongArch, not MIPS)support. LoongArch use ACPI other than DT as its boot protocol, soadd its support for ACPI_PROCESSOR/ACPI_NUMA.Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/numa/Kconfig</description>
        <pubDate>Mon, 05 Jul 2021 12:42:04 +0000</pubDate>
        <dc:creator>Huacai Chen &lt;chenhuacai@loongson.cn&gt;</dc:creator>
    </item>
<item>
        <title>cf8741ac - ACPI: NUMA: HMAT: Register &quot;soft reserved&quot; memory as an &quot;hmem&quot; device</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/numa/Kconfig#cf8741ac</link>
        <description>ACPI: NUMA: HMAT: Register &quot;soft reserved&quot; memory as an &quot;hmem&quot; deviceMemory that has been tagged EFI_MEMORY_SP, and has performanceproperties described by the ACPI HMAT is expected to have an applicationspecific consumer.Those consumers may want 100% of the memory capacity to be reserved fromany usage by the kernel. By default, with this enabling, a platformdevice is created to represent this differentiated resource.The device-dax &quot;hmem&quot; driver claims these devices by default andprovides an mmap interface for the target application.  If theadministrator prefers, the hmem resource range can be made available tothe core-mm via the device-dax hotplug facility, kmem, to online thememory with its own numa node.This was tested with an emulated HMAT produced by qemu (with the pendingHMAT enabling patches), and &quot;efi_fake_mem=8G@9G:0x40000&quot; on the kernelcommand line to mark the memory ranges associated with node2 and node3as EFI_MEMORY_SP.qemu numa configuration options:-numa node,mem=4G,cpus=0-19,nodeid=0-numa node,mem=4G,cpus=20-39,nodeid=1-numa node,mem=4G,nodeid=2-numa node,mem=4G,nodeid=3-numa dist,src=0,dst=0,val=10-numa dist,src=0,dst=1,val=21-numa dist,src=0,dst=2,val=21-numa dist,src=0,dst=3,val=21-numa dist,src=1,dst=0,val=21-numa dist,src=1,dst=1,val=10-numa dist,src=1,dst=2,val=21-numa dist,src=1,dst=3,val=21-numa dist,src=2,dst=0,val=21-numa dist,src=2,dst=1,val=21-numa dist,src=2,dst=2,val=10-numa dist,src=2,dst=3,val=21-numa dist,src=3,dst=0,val=21-numa dist,src=3,dst=1,val=21-numa dist,src=3,dst=2,val=21-numa dist,src=3,dst=3,val=10-numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-latency,base-lat=10,latency=5-numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=5-numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-latency,base-lat=10,latency=10-numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=10-numa hmat-lb,initiator=0,target=2,hierarchy=memory,data-type=access-latency,base-lat=10,latency=15-numa hmat-lb,initiator=0,target=2,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=15-numa hmat-lb,initiator=0,target=3,hierarchy=memory,data-type=access-latency,base-lat=10,latency=20-numa hmat-lb,initiator=0,target=3,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=20-numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-latency,base-lat=10,latency=10-numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=10-numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-latency,base-lat=10,latency=5-numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=5-numa hmat-lb,initiator=1,target=2,hierarchy=memory,data-type=access-latency,base-lat=10,latency=15-numa hmat-lb,initiator=1,target=2,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=15-numa hmat-lb,initiator=1,target=3,hierarchy=memory,data-type=access-latency,base-lat=10,latency=20-numa hmat-lb,initiator=1,target=3,hierarchy=memory,data-type=access-bandwidth,base-bw=20,bandwidth=20Result:[  {    &quot;path&quot;:&quot;\/platform\/hmem.1&quot;,    &quot;id&quot;:1,    &quot;size&quot;:&quot;4.00 GiB (4.29 GB)&quot;,    &quot;align&quot;:2097152,    &quot;devices&quot;:[      {        &quot;chardev&quot;:&quot;dax1.0&quot;,        &quot;size&quot;:&quot;4.00 GiB (4.29 GB)&quot;      }    ]  },  {    &quot;path&quot;:&quot;\/platform\/hmem.0&quot;,    &quot;id&quot;:0,    &quot;size&quot;:&quot;4.00 GiB (4.29 GB)&quot;,    &quot;align&quot;:2097152,    &quot;devices&quot;:[      {        &quot;chardev&quot;:&quot;dax0.0&quot;,        &quot;size&quot;:&quot;4.00 GiB (4.29 GB)&quot;      }    ]  }][..]240000000-43fffffff : Soft Reserved  240000000-33fffffff : hmem.0    240000000-33fffffff : dax0.0  340000000-43fffffff : hmem.1    340000000-43fffffff : dax1.0Reviewed-by: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/numa/Kconfig</description>
        <pubDate>Thu, 07 Nov 2019 01:43:55 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c710fcc5 - ACPI: NUMA: Establish a new drivers/acpi/numa/ directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/numa/Kconfig#c710fcc5</link>
        <description>ACPI: NUMA: Establish a new drivers/acpi/numa/ directoryCurrently hmat.c lives under an &quot;hmat&quot; directory which does not enhancethe description of the file. The initial motivation for giving hmat.cits own directory was to delineate it as mm functionality in contrast toACPI device driver functionality.As ACPI continues to play an increasing role in conveyingmemory location and performance topology information to the OS take theopportunity to co-locate these NUMA relevant tables in a combineddirectory.numa.c is renamed to srat.c and moved to drivers/acpi/numa/ along withhmat.c.Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/numa/Kconfig</description>
        <pubDate>Thu, 07 Nov 2019 01:42:55 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
