<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a79be02b - Fix mis-uses of &apos;cc-option&apos; for warning disablement</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#a79be02b</link>
        <description>Fix mis-uses of &apos;cc-option&apos; for warning disablementThis was triggered by one of my mis-uses causing odd build warnings onsparc in linux-next, but while figuring out why the &quot;obviously correct&quot;use of cc-option caused such odd breakage, I found eight other cases ofthe same thing in the tree.The root cause is that &apos;cc-option&apos; doesn&apos;t work for checking negativewarning options (ie things like &apos;-Wno-stringop-overflow&apos;) because gccwill silently accept options it doesn&apos;t recognize, and so &apos;cc-option&apos;ends up thinking they are perfectly fine.And it all works, until you have a situation where _another_ warning isemitted.  At that point the compiler will go &quot;Hmm, maybe the userintended to disable this warning but used that wrong option that Ididn&apos;t recognize&quot;, and generate a warning for the unrecognized negativeoption.Which explains why we have several cases of this in the tree: the&apos;cc-option&apos; test really doesn&apos;t work for this situation, but most of thetime it simply doesn&apos;t matter that ity doesn&apos;t work.The reason my recently added case caused problems on sparc was pointedout by Thomas Wei&#223;schuh: the sparc build had a previous explicit warningthat then triggered the new one.I think the best fix for this would be to make &apos;cc-option&apos; a bit smarterabout this sitation, possibly by adding an intentional warning to thetest case that then triggers the unrecognized option warning reliably.But the short-term fix is to replace &apos;cc-option&apos; with an existing helperdesigned for this exact case: &apos;cc-disable-warning&apos;, which picks thenegative warning but uses the positive form for testing the compilersupport.Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Link: https://lore.kernel.org/all/20250422204718.0b4e3f81@canb.auug.org.au/Explained-by: Thomas Wei&#223;schuh &lt;linux@weissschuh.net&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 23 Apr 2025 17:08:29 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>4bf97069 - riscv: Add ghostwrite vulnerability</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#4bf97069</link>
        <description>riscv: Add ghostwrite vulnerabilityFollow the patterns of the other architectures that useGENERIC_CPU_VULNERABILITIES for riscv to introduce the ghostwritevulnerability and mitigation. The mitigation is to disable all vectorwhich is accomplished by clearing the bit from the cpufeature field.Ghostwrite only affects thead c9xx CPUs that impelment xtheadvector, sothe vulerability will only be mitigated on these CPUs.Signed-off-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Tested-by: Yangyu Chen &lt;cyy@cyyself.name&gt;Link: https://lore.kernel.org/r/20241113-xtheadvector-v11-14-236c22791ef9@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 14 Nov 2024 02:21:20 +0000</pubDate>
        <dc:creator>Charlie Jenkins &lt;charlie@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>afedc312 - riscv: Do not use fortify in early code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#afedc312</link>
        <description>riscv: Do not use fortify in early codeEarly code designates the code executed when the MMU is not yet enabled,and this comes with some limitations (seeDocumentation/arch/riscv/boot.rst, section &quot;Pre-MMU execution&quot;).FORTIFY_SOURCE must be disabled then since it can trigger kernel panicsas reported in [1].Reported-by: Jason Montleon &lt;jmontleo@redhat.com&gt;Closes: https://lore.kernel.org/linux-riscv/CAJD_bPJes4QhmXY5f63GHV9B9HFkSCoaZjk-qCT2NGS7Q9HODg@mail.gmail.com/ [1]Fixes: a35707c3d850 (&quot;riscv: add memory-type errata for T-Head&quot;)Fixes: 26e7aacb83df (&quot;riscv: Allow to downgrade paging mode from the command line&quot;)Cc: stable@vger.kernel.orgSigned-off-by: Alexandre Ghiti &lt;alexghiti@rivosinc.com&gt;Link: https://lore.kernel.org/r/20241009072749.45006-1-alexghiti@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 09 Oct 2024 07:27:49 +0000</pubDate>
        <dc:creator>Alexandre Ghiti &lt;alexghiti@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>e7c9d66e - RISC-V: Report vector unaligned access speed hwprobe</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#e7c9d66e</link>
        <description>RISC-V: Report vector unaligned access speed hwprobeDetect if vector misaligned accesses are faster or slower thanequivalent vector byte accesses. This is useful for usermode to knowwhether vector byte accesses or vector misaligned accesses have a betterbandwidth for operations like memcpy.Signed-off-by: Jesse Taube &lt;jesse@rivosinc.com&gt;Reviewed-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Link: https://lore.kernel.org/r/20241017-jesse_unaligned_vector-v10-5-5b33500160f8@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 17 Oct 2024 19:00:22 +0000</pubDate>
        <dc:creator>Jesse Taube &lt;jesse@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>d1703dc7 - RISC-V: Detect unaligned vector accesses supported</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#d1703dc7</link>
        <description>RISC-V: Detect unaligned vector accesses supportedRun an unaligned vector access to test if the system supportsvector unaligned access. Add the result to a new key in hwprobe.This is useful for usermode to know if vector misaligned accesses aresupported and if they are faster or slower than equivalent byte accesses.Signed-off-by: Jesse Taube &lt;jesse@rivosinc.com&gt;Signed-off-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Link: https://lore.kernel.org/r/20241017-jesse_unaligned_vector-v10-4-5b33500160f8@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 17 Oct 2024 19:00:21 +0000</pubDate>
        <dc:creator>Jesse Taube &lt;jesse@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>c05a62c9 - RISC-V: Replace RISCV_MISALIGNED with RISCV_SCALAR_MISALIGNED</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#c05a62c9</link>
        <description>RISC-V: Replace RISCV_MISALIGNED with RISCV_SCALAR_MISALIGNEDReplace RISCV_MISALIGNED with RISCV_SCALAR_MISALIGNED to allowfor the addition of RISCV_VECTOR_MISALIGNED in a later patch.Signed-off-by: Jesse Taube &lt;jesse@rivosinc.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Reviewed-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Reviewed-by: Evan Green &lt;evan@rivosinc.com&gt;Link: https://lore.kernel.org/r/20241017-jesse_unaligned_vector-v10-3-5b33500160f8@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 17 Oct 2024 19:00:20 +0000</pubDate>
        <dc:creator>Jesse Taube &lt;jesse@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>1ff95eb2 - riscv: Fix RISCV_ALTERNATIVE_EARLY</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#1ff95eb2</link>
        <description>riscv: Fix RISCV_ALTERNATIVE_EARLYRISCV_ALTERNATIVE_EARLY will issue sbi_ecall() very early in the bootprocess, before the first memory mapping is setup so we can&apos;t have anyinstrumentation happening here.In addition, when the kernel is relocatable, we must also not issue anyrelocation this early since they would have been patched virtually only.So, instead of disabling instrumentation for the whole kernel/sbi.c fileand compiling it with -fno-pie, simply move __sbi_ecall() and__sbi_base_ecall() into their own file where this is fixed.Reported-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Closes: https://lore.kernel.org/linux-riscv/20240813-pony-truck-3e7a83e9759e@spud/Reported-by: syzbot+cfbcb82adf6d7279fd35@syzkaller.appspotmail.comCloses: https://lore.kernel.org/linux-riscv/00000000000065062c061fcec37b@google.com/Fixes: 1745cfafebdf (&quot;riscv: don&apos;t use global static vars to store alternative data&quot;)Signed-off-by: Alexandre Ghiti &lt;alexghiti@rivosinc.com&gt;Link: https://lore.kernel.org/r/20240829165048.49756-1-alexghiti@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 29 Aug 2024 16:50:48 +0000</pubDate>
        <dc:creator>Alexandre Ghiti &lt;alexghiti@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>23c996fc - riscv: Extend cpufeature.c to detect vendor extensions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#23c996fc</link>
        <description>riscv: Extend cpufeature.c to detect vendor extensionsInstead of grouping all vendor extensions into the same riscv_isa_extthat standard instructions use, create a struct&quot;riscv_isa_vendor_ext_data_list&quot; that allows each vendor to maintaintheir vendor extensions independently of the standard extensions.xandespmu is currently the only vendor extension so that is the onlyextension that is affected by this change.An additional benefit of this is that the extensions of each vendor canbe conditionally enabled. A config RISCV_ISA_VENDOR_EXT_ANDES has beenadded to allow for that.Signed-off-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Reviewed-by: Andy Chiu &lt;andy.chiu@sifive.com&gt;Tested-by: Yu Chien Peter Lin &lt;peterlin@andestech.com&gt;Reviewed-by: Yu Chien Peter Lin &lt;peterlin@andestech.com&gt;Link: https://lore.kernel.org/r/20240719-support_vendor_extensions-v3-1-0af7587bbec0@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 19 Jul 2024 16:15:18 +0000</pubDate>
        <dc:creator>Charlie Jenkins &lt;charlie@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>eabd9db6 - ACPI: RISCV: Add NUMA support based on SRAT and SLIT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#eabd9db6</link>
        <description>ACPI: RISCV: Add NUMA support based on SRAT and SLITAdd acpi_numa.c file to enable parse NUMA information fromACPI SRAT and SLIT tables. SRAT table provide CPUs(Hart) andmemory nodes to proximity domain mapping, while SLIT tableprovide the distance metrics between proximity domains.Signed-off-by: Haibo Xu &lt;haibo1.xu@intel.com&gt;Reviewed-by: Sunil V L &lt;sunilvl@ventanamicro.com&gt;Reviewed-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;Link: https://lore.kernel.org/r/65dbad1fda08a32922c44886e4581e49b4a2fecc.1718268003.git.haibo1.xu@intel.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Thu, 13 Jun 2024 08:54:33 +0000</pubDate>
        <dc:creator>Haibo Xu &lt;haibo1.xu@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>77acc6b5 - riscv: add support for kernel-mode FPU</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#77acc6b5</link>
        <description>riscv: add support for kernel-mode FPUThis is motivated by the amdgpu DRM driver, which needs floating-pointcode to support recent hardware.  That code is not performance-critical,so only provide a minimal non-preemptible implementation for now.Support is limited to riscv64 because riscv32 requires runtime (libgcc)assistance to convert between doubles and 64-bit integers.Link: https://lkml.kernel.org/r/20240329072441.591471-12-samuel.holland@sifive.comSigned-off-by: Samuel Holland &lt;samuel.holland@sifive.com&gt;Acked-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;Reviewed-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Acked-by: Christian K&#246;nig &lt;christian.koenig@amd.com&gt; Cc: Alex Deucher &lt;alexander.deucher@amd.com&gt;Cc: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;Cc: Huacai Chen &lt;chenhuacai@kernel.org&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Nathan Chancellor &lt;nathan@kernel.org&gt;Cc: Nicolas Schier &lt;nicolas@fjasle.eu&gt;Cc: Russell King &lt;linux@armlinux.org.uk&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: WANG Xuerui &lt;git@xen0n.name&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/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 29 Mar 2024 07:18:26 +0000</pubDate>
        <dc:creator>Samuel Holland &lt;samuel.holland@sifive.com&gt;</dc:creator>
    </item>
<item>
        <title>f413aae9 - riscv: Set unaligned access speed at compile time</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#f413aae9</link>
        <description>riscv: Set unaligned access speed at compile timeIntroduce Kconfig options to set the kernel unaligned access support.These options provide a non-portable alternative to the runtimeunaligned access probe.To support this, the unaligned access probing code is moved into it&apos;sown file and gated behind a new RISCV_PROBE_UNALIGNED_ACCESS_SUPPORToption.Signed-off-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Tested-by: Samuel Holland &lt;samuel.holland@sifive.com&gt;Link: https://lore.kernel.org/r/20240308-disable_misaligned_probe_config-v9-4-a388770ba0ce@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 08 Mar 2024 18:25:58 +0000</pubDate>
        <dc:creator>Charlie Jenkins &lt;charlie@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>443cbaf9 - crash: split vmcoreinfo exporting code out from crash_core.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#443cbaf9</link>
        <description>crash: split vmcoreinfo exporting code out from crash_core.cNow move the relevant codes into separate files:kernel/crash_reserve.c, include/linux/crash_reserve.h.And add config item CRASH_RESERVE to control its enabling.And also update the old ifdeffery of CONFIG_CRASH_CORE, including of&lt;linux/crash_core.h&gt; and config item dependency on CRASH_COREaccordingly.And also do renaming as follows: - arch/xxx/kernel/{crash_core.c =&gt; vmcore_info.c}because they are only related to vmcoreinfo exporting on x86, arm64,riscv.And also Remove config item CRASH_CORE, and rely on CONFIG_KEXEC_CORE todecide if build in crash_core.c.[yang.lee@linux.alibaba.com: remove duplicated include in vmcore_info.c]  Link: https://lkml.kernel.org/r/20240126005744.16561-1-yang.lee@linux.alibaba.comLink: https://lkml.kernel.org/r/20240124051254.67105-3-bhe@redhat.comSigned-off-by: Baoquan He &lt;bhe@redhat.com&gt;Signed-off-by: Yang Li &lt;yang.lee@linux.alibaba.com&gt;Acked-by: Hari Bathini &lt;hbathini@linux.ibm.com&gt;Cc: Al Viro &lt;viro@zeniv.linux.org.uk&gt;Cc: Eric W. Biederman &lt;ebiederm@xmission.com&gt;Cc: Pingfan Liu &lt;piliu@redhat.com&gt;Cc: Klara Modin &lt;klarasmodin@gmail.com&gt;Cc: Michael Kelley &lt;mhklinux@outlook.com&gt;Cc: Nathan Chancellor &lt;nathan@kernel.org&gt;Cc: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Cc: Yang Li &lt;yang.lee@linux.alibaba.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 24 Jan 2024 05:12:42 +0000</pubDate>
        <dc:creator>Baoquan He &lt;bhe@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>68034138 - riscv: add CALLER_ADDRx support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#68034138</link>
        <description>riscv: add CALLER_ADDRx supportCALLER_ADDRx returns caller&apos;s address at specified level, they are usedfor several tracers. These macros eventually use__builtin_return_address(n) to get the caller&apos;s address if arch doesn&apos;tdefine their own implementation.In RISC-V, __builtin_return_address(n) only works when n == 0, we needto walk the stack frame to get the caller&apos;s address at specified level.data.level started from &apos;level + 3&apos; due to the call flow of gettingcaller&apos;s address in RISC-V implementation. If we don&apos;t have additionalthree iteration, the level is corresponding to follows:callsite -&gt; return_address -&gt; arch_stack_walk -&gt; walk_stackframe|           |                 |                  |level 3     level 2           level 1            level 0Fixes: 10626c32e382 (&quot;riscv/ftrace: Add basic support&quot;)Cc: stable@vger.kernel.orgReviewed-by: Alexandre Ghiti &lt;alexghiti@rivosinc.com&gt;Signed-off-by: Zong Li &lt;zong.li@sifive.com&gt;Link: https://lore.kernel.org/r/20240202015102.26251-1-zong.li@sifive.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 02 Feb 2024 01:51:02 +0000</pubDate>
        <dc:creator>Zong Li &lt;zong.li@sifive.com&gt;</dc:creator>
    </item>
<item>
        <title>ecd2ada8 - riscv: Add support for kernel mode vector</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#ecd2ada8</link>
        <description>riscv: Add support for kernel mode vectorAdd kernel_vector_begin() and kernel_vector_end() function declarationsand corresponding definitions in kernel_mode_vector.cThese are needed to wrap uses of vector in kernel mode.Co-developed-by: Vincent Chen &lt;vincent.chen@sifive.com&gt;Signed-off-by: Vincent Chen &lt;vincent.chen@sifive.com&gt;Signed-off-by: Greentime Hu &lt;greentime.hu@sifive.com&gt;Signed-off-by: Andy Chiu &lt;andy.chiu@sifive.com&gt;Reviewed-by: Eric Biggers &lt;ebiggers@google.com&gt;Tested-by: Bj&#246;rn T&#246;pel &lt;bjorn@rivosinc.com&gt;Tested-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;Link: https://lore.kernel.org/r/20240115055929.4736-2-andy.chiu@sifive.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Mon, 15 Jan 2024 05:59:20 +0000</pubDate>
        <dc:creator>Greentime Hu &lt;greentime.hu@sifive.com&gt;</dc:creator>
    </item>
<item>
        <title>53b2b228 - RISC-V: Move the hwprobe syscall to its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#53b2b228</link>
        <description>RISC-V: Move the hwprobe syscall to its own fileAs Palmer says, hwprobe is &quot;sort of its own thing now, and it&apos;s onlygoing to get bigger...&quot;Suggested-by: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Signed-off-by: Andrew Jones &lt;ajones@ventanamicro.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Link: https://lore.kernel.org/r/20231122164700.127954-8-ajones@ventanamicro.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 22 Nov 2023 16:47:03 +0000</pubDate>
        <dc:creator>Andrew Jones &lt;ajones@ventanamicro.com&gt;</dc:creator>
    </item>
<item>
        <title>323925ed - RISC-V: paravirt: Add skeleton for pv-time support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#323925ed</link>
        <description>RISC-V: paravirt: Add skeleton for pv-time supportAdd the files and functions needed to support paravirt time onRISC-V. Also include the common code needed for the firstapplication of pv-time, which is steal-time. In the nextpatches we&apos;ll complete the functions to fully enable steal-timesupport.Acked-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;Reviewed-by: Anup Patel &lt;anup@brainfault.org&gt;Reviewed-by: Atish Patra &lt;atishp@rivosinc.com&gt;Signed-off-by: Andrew Jones &lt;ajones@ventanamicro.com&gt;Signed-off-by: Anup Patel &lt;anup@brainfault.org&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 20 Dec 2023 16:00:14 +0000</pubDate>
        <dc:creator>Andrew Jones &lt;ajones@ventanamicro.com&gt;</dc:creator>
    </item>
<item>
        <title>d53a154c - riscv, kexec: fix the ifdeffery for AFLAGS_kexec_relocate.o</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#d53a154c</link>
        <description>riscv, kexec: fix the ifdeffery for AFLAGS_kexec_relocate.oThis was introduced in commit fba8a8674f68 (&quot;RISC-V: Add kexecsupport&quot;).It should work on CONFIG_KEXEC_CORE, but not CONFIG_KEXEC only, sincewe could set CONFIG_KEXEC_FILE=y and CONFIG_KEXEC=N, or only setCONFIG_CRASH_DUMP=y and disable both CONFIG_KEXEC and CONFIG_KEXEC_FILE.In these cases, the AFLAGS won&apos;t take effect with the current ifdefferyfor AFLAGS_kexec_relocate.o.So fix it now.Link: https://lkml.kernel.org/r/20231201062538.27240-1-bhe@redhat.comSigned-off-by: Baoquan He &lt;bhe@redhat.com&gt;Cc: Albert Ou &lt;aou@eecs.berkeley.edu&gt;Cc: Changbin Du &lt;changbin.du@intel.com&gt;Cc: Nick Kossifidis &lt;mick@ics.forth.gr&gt;Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Cc: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 01 Dec 2023 06:25:38 +0000</pubDate>
        <dc:creator>Baoquan He &lt;bhe@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>af71bc19 - riscv: Add tests for riscv module loading</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#af71bc19</link>
        <description>riscv: Add tests for riscv module loadingAdd test cases for the two main groups of relocations added: SUB andSET, along with uleb128.Signed-off-by: Charlie Jenkins &lt;charlie@rivosinc.com&gt;Link: https://lore.kernel.org/r/20231101-module_relocations-v9-3-8dfa3483c400@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 01 Nov 2023 18:33:01 +0000</pubDate>
        <dc:creator>Charlie Jenkins &lt;charlie@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>7c832321 - riscv: add support for misaligned trap handling in S-mode</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#7c832321</link>
        <description>riscv: add support for misaligned trap handling in S-modeMisalignment trap handling is only supported for M-mode and uses directaccesses to user memory. In S-mode, when handling usermode fault, thisrequires to use the get_user()/put_user() accessors. Implementload_u8(), store_u8() and get_insn() using these accessors foruserspace and direct text access for kernel.Signed-off-by: Cl&#233;ment L&#233;ger &lt;cleger@rivosinc.com&gt;Reviewed-by: Bj&#246;rn T&#246;pel &lt;bjorn@rivosinc.com&gt;Link: https://lore.kernel.org/r/20231004151405.521596-3-cleger@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Wed, 04 Oct 2023 15:13:59 +0000</pubDate>
        <dc:creator>Cl&#233;ment L&#233;ger &lt;cleger@rivosinc.com&gt;</dc:creator>
    </item>
<item>
        <title>584ea656 - RISC-V: Probe for unaligned access speed</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/riscv/kernel/Makefile#584ea656</link>
        <description>RISC-V: Probe for unaligned access speedRather than deferring unaligned access speed determinations to a vendorfunction, let&apos;s probe them and find out how fast they are. If wedetermine that an unaligned word access is faster than N byte accesses,mark the hardware&apos;s unaligned access as &quot;fast&quot;. Otherwise, we markaccesses as slow.The algorithm itself runs for a fixed amount of jiffies. Within eachiteration it attempts to time a single loop, and then keeps only the best(fastest) loop it saw. This algorithm was found to have lower variance fromrun to run than my first attempt, which counted the total number ofiterations that could be done in that fixed amount of jiffies. By takingonly the best iteration in the loop, assuming at least one loop wasn&apos;tperturbed by an interrupt, we eliminate the effects of interrupts andother &quot;warm up&quot; factors like branch prediction. The only downside is itdepends on having an rdtime granular and accurate enough to measure asingle copy. If we ever manage to complete a loop in 0 rdtime ticks, weleave the unaligned setting at UNKNOWN.There is a slight change in user-visible behavior here. Previously, allboards except the THead C906 reported misaligned access speed ofUNKNOWN. C906 reported FAST. With this change, since we&apos;re now measuringmisaligned access speed on each hart, all RISC-V systems will have thiskey set as either FAST or SLOW.Currently, we don&apos;t have a way to confidently measure the difference betweenSLOW and EMULATED, so we label anything not fast as SLOW. This willmislabel some systems that are actually EMULATED as SLOW. When we getsupport for delegating misaligned access traps to the kernel (as opposedto the firmware quietly handling it), we can explicitly test in Linux tosee if unaligned accesses trap. Those systems will start to reportEMULATED, though older (today&apos;s) systems without that new SBI mechanismwill continue to report SLOW.I&apos;ve updated the documentation for those hwprobe values to reflectthis, specifically: SLOW may or may not be emulated by software, and FASTrepresents means being faster than equivalent byte accesses. The changein documentation is accurate with respect to both the former and currentbehavior.Signed-off-by: Evan Green &lt;evan@rivosinc.com&gt;Acked-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Link: https://lore.kernel.org/r/20230818194136.4084400-2-evan@rivosinc.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/arch/riscv/kernel/Makefile</description>
        <pubDate>Fri, 18 Aug 2023 19:41:35 +0000</pubDate>
        <dc:creator>Evan Green &lt;evan@rivosinc.com&gt;</dc:creator>
    </item>
</channel>
</rss>
