<?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.vmlinux_o</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>e0cd396d - kbuild: fix typos &quot;module.builtin&quot; to &quot;modules.builtin&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#e0cd396d</link>
        <description>kbuild: fix typos &quot;module.builtin&quot; to &quot;modules.builtin&quot;The filenames in the comments do not match the actual generated files.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Mon, 12 May 2025 05:36:58 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>876a4bce - objtool: Remove --no-unreachable for noinstr-only vmlinux.o runs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#876a4bce</link>
        <description>objtool: Remove --no-unreachable for noinstr-only vmlinux.o runsFor (!X86_KERNEL_IBT &amp;&amp; !LTO_CLANG &amp;&amp; NOINSTR_VALIDATION), objtool runson both translation units and vmlinux.o.  The vmlinux.o run only doesnoinstr/noret validation.  In that case --no-unreachable has no effect.Remove it.Note that for ((X86_KERNEL_IBT || LTO_CLANG) &amp;&amp; KCOV), --no-unreachablestill gets set in objtool-args-y by scripts/Makefile.lib.Signed-off-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Link: https://lore.kernel.org/r/05414246a0124db2f21b0d071b652aa9043d039d.1742852847.git.jpoimboe@kernel.org

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Mon, 24 Mar 2025 21:56:02 +0000</pubDate>
        <dc:creator>Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>4759670b - objtool: Fix CONFIG_OBJTOOL_WERROR for vmlinux.o</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#4759670b</link>
        <description>objtool: Fix CONFIG_OBJTOOL_WERROR for vmlinux.oWith (!X86_KERNEL_IBT &amp;&amp; !LTO_CLANG &amp;&amp; NOINSTR_VALIDATION), objtool runson both translation units and vmlinux.o.  With CONFIG_OBJTOOL_WERROR,the TUs get --Werror but vmlinux.o doesn&apos;t.  Fix that.Signed-off-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Link: https://lore.kernel.org/r/4f71ab9b947ffc47b6a87dd3b9aff4bb32b36d0a.1742852846.git.jpoimboe@kernel.org

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Mon, 24 Mar 2025 21:55:55 +0000</pubDate>
        <dc:creator>Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5f5e7344 - kbuild: generate offset range data for builtin modules</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#5f5e7344</link>
        <description>kbuild: generate offset range data for builtin modulesCreate file module.builtin.ranges that can be used to find wherebuilt-in modules are located by their addresses. This will be useful fortracing tools to find what functions are for various built-in modules.The offset range data for builtin modules is generated using: - modules.builtin: associates object files with module names - vmlinux.map: provides load order of sections and offset of first member    per section - vmlinux.o.map: provides offset of object file content per section - .*.cmd: build cmd file with KBUILD_MODFILEThe generated data will look like:.text 00000000-00000000 = _text.text 0000baf0-0000cb10 amd_uncore.text 0009bd10-0009c8e0 iosf_mbi....text 00b9f080-00ba011a intel_skl_int3472_discrete.text 00ba0120-00ba03c0 intel_skl_int3472_discrete intel_skl_int3472_tps68470.text 00ba03c0-00ba08d6 intel_skl_int3472_tps68470....data 00000000-00000000 = _sdata.data 0000f020-0000f680 amd_uncoreFor each ELF section, it lists the offset of the first symbol.  This canbe used to determine the base address of the section at runtime.Next, it lists (in strict ascending order) offset ranges in that sectionthat cover the symbols of one or more builtin modules.  Multiple rangescan apply to a single module, and ranges can be shared between modules.The CONFIG_BUILTIN_MODULE_RANGES option controls whether offset range datais generated for kernel modules that are built into the kernel image.How it works: 1. The modules.builtin file is parsed to obtain a list of built-in    module names and their associated object names (the .ko file that    the module would be in if it were a loadable module, hereafter    referred to as &lt;kmodfile&gt;).  This object name can be used to    identify objects in the kernel compile because any C or assembler    code that ends up into a built-in module will have the option    -DKBUILD_MODFILE=&lt;kmodfile&gt; present in its build command, and those    can be found in the .&lt;obj&gt;.cmd file in the kernel build tree.    If an object is part of multiple modules, they will all be listed    in the KBUILD_MODFILE option argument.    This allows us to conclusively determine whether an object in the    kernel build belong to any modules, and which. 2. The vmlinux.map is parsed next to determine the base address of each    top level section so that all addresses into the section can be    turned into offsets.  This makes it possible to handle sections    getting loaded at different addresses at system boot.    We also determine an &apos;anchor&apos; symbol at the beginning of each    section to make it possible to calculate the true base address of    a section at runtime (i.e. symbol address - symbol offset).    We collect start addresses of sections that are included in the top    level section.  This is used when vmlinux is linked using vmlinux.o,    because in that case, we need to look at the vmlinux.o linker map to    know what object a symbol is found in.    And finally, we process each symbol that is listed in vmlinux.map    (or vmlinux.o.map) based on the following structure:    vmlinux linked from vmlinux.a:      vmlinux.map:        &lt;top level section&gt;          &lt;included section&gt;  -- might be same as top level section)            &lt;object&gt;          -- built-in association known              &lt;symbol&gt;        -- belongs to module(s) object belongs to              ...    vmlinux linked from vmlinux.o:      vmlinux.map:        &lt;top level section&gt;          &lt;included section&gt;  -- might be same as top level section)            vmlinux.o         -- need to use vmlinux.o.map              &lt;symbol&gt;        -- ignored              ...      vmlinux.o.map:        &lt;section&gt;            &lt;object&gt;          -- built-in association known              &lt;symbol&gt;        -- belongs to module(s) object belongs to              ... 3. As sections, objects, and symbols are processed, offset ranges are    constructed in a straight-forward way:      - If the symbol belongs to one or more built-in modules:          - If we were working on the same module(s), extend the range            to include this object          - If we were working on another module(s), close that range,            and start the new one      - If the symbol does not belong to any built-in modules:          - If we were working on a module(s) range, close that rangeSigned-off-by: Kris Van Hees &lt;kris.van.hees@oracle.com&gt;Reviewed-by: Nick Alcock &lt;nick.alcock@oracle.com&gt;Reviewed-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Steven Rostedt (Google) &lt;rostedt@goodmis.org&gt;Tested-by: Sam James &lt;sam@gentoo.org&gt;Reviewed-by: Sami Tolvanen &lt;samitolvanen@google.com&gt;Tested-by: Sami Tolvanen &lt;samitolvanen@google.com&gt;Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Fri, 06 Sep 2024 14:45:03 +0000</pubDate>
        <dc:creator>Kris Van Hees &lt;kris.van.hees@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>8fb4ac1c - kbuild: fix typos &quot;prequisites&quot; to &quot;prerequisites&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#8fb4ac1c</link>
        <description>kbuild: fix typos &quot;prequisites&quot; to &quot;prerequisites&quot;This typo in scripts/Makefile.build has been present for more than 20years. It was accidentally copy-pasted to other scripts/Makefile.* files.Fix them all.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Nathan Chancellor &lt;nathan@kernel.org&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Sun, 18 Aug 2024 07:07:11 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>a033eec9 - x86/bugs: Rename CONFIG_CPU_SRSO             =&gt; CONFIG_MITIGATION_SRSO</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#a033eec9</link>
        <description>x86/bugs: Rename CONFIG_CPU_SRSO             =&gt; CONFIG_MITIGATION_SRSOStep 9/10 of the namespace unification of CPU mitigations related Kconfig options.Suggested-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Breno Leitao &lt;leitao@debian.org&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Acked-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Link: https://lore.kernel.org/r/20231121160740.1249350-10-leitao@debian.org

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Tue, 21 Nov 2023 16:07:36 +0000</pubDate>
        <dc:creator>Breno Leitao &lt;leitao@debian.org&gt;</dc:creator>
    </item>
<item>
        <title>ac61d439 - x86/bugs: Rename CONFIG_CPU_UNRET_ENTRY      =&gt; CONFIG_MITIGATION_UNRET_ENTRY</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#ac61d439</link>
        <description>x86/bugs: Rename CONFIG_CPU_UNRET_ENTRY      =&gt; CONFIG_MITIGATION_UNRET_ENTRYStep 7/10 of the namespace unification of CPU mitigations related Kconfig options.Suggested-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Breno Leitao &lt;leitao@debian.org&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Acked-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Link: https://lore.kernel.org/r/20231121160740.1249350-8-leitao@debian.org

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Tue, 21 Nov 2023 16:07:34 +0000</pubDate>
        <dc:creator>Breno Leitao &lt;leitao@debian.org&gt;</dc:creator>
    </item>
<item>
        <title>eeb9f34d - x86/srso: Fix unret validation dependencies</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#eeb9f34d</link>
        <description>x86/srso: Fix unret validation dependenciesCONFIG_CPU_SRSO isn&apos;t dependent on CONFIG_CPU_UNRET_ENTRY (AMDRetbleed), so the two features are independently configurable.  Fixseveral issues for the (presumably rare) case where CONFIG_CPU_SRSO isenabled but CONFIG_CPU_UNRET_ENTRY isn&apos;t.Fixes: fb3bd914b3ec (&quot;x86/srso: Add a Speculative RAS Overflow mitigation&quot;)Signed-off-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Acked-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Link: https://lore.kernel.org/r/299fb7740174d0f2335e91c58af0e9c242b4bac1.1693889988.git.jpoimboe@kernel.org

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Tue, 05 Sep 2023 05:04:53 +0000</pubDate>
        <dc:creator>Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7a342e6c - kbuild: move modules.builtin(.modinfo) rules to Makefile.vmlinux_o</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#7a342e6c</link>
        <description>kbuild: move modules.builtin(.modinfo) rules to Makefile.vmlinux_oDo not build modules.builtin(.modinfo) as a side-effect of vmlinux.There are no good reason to rebuild them just because any of vmlinux&apos;sprerequistes (vmlinux.lds, .vmlinux.export.c, etc.) has been updated.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Wed, 28 Sep 2022 06:39:40 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>32164845 - kbuild: use obj-y instead extra-y for objects placed at the head</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#32164845</link>
        <description>kbuild: use obj-y instead extra-y for objects placed at the headThe objects placed at the head of vmlinux need special treatments: - arch/$(SRCARCH)/Makefile adds them to head-y in order to place   them before other archives in the linker command line. - arch/$(SRCARCH)/kernel/Makefile adds them to extra-y instead of   obj-y to avoid them going into built-in.a.This commit gets rid of the latter.Create vmlinux.a to collect all the objects that are unconditionallylinked to vmlinux. The objects listed in head-y are moved to the headof vmlinux.a by using &apos;ar m&apos;.With this, arch/$(SRCARCH)/kernel/Makefile can consistently use obj-yfor builtin objects.There is no *.o that is directly linked to vmlinux. Drop unneeded codein scripts/clang-tools/gen_compile_commands.py.$(AR) mPi needs &apos;T&apos; to workaround the llvm-ar bug. The fix was suggestedby Nathan Chancellor [1].[1]: https://lore.kernel.org/llvm/YyjjT5gQ2hGMH0ni@dev-arch.thelio-3990X/Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Sat, 24 Sep 2022 18:19:14 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>9ec6ab6e - kbuild: use objtool-args-y to clean up objtool arguments</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#9ec6ab6e</link>
        <description>kbuild: use objtool-args-y to clean up objtool argumentsBased on Linus&apos; patch. Refactor scripts/Makefile.vmlinux_o as well.Link: https://lore.kernel.org/lkml/CAHk-=wgjTMQgiKzBZTmb=uWGDEQxDdyF1+qxBkODYciuNsmwnw@mail.gmail.com/Suggested-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Acked-by: Peter Zijlstra &lt;peterz@infradead.org&gt;Reviewed-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Tue, 06 Sep 2022 18:49:35 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f43b9876 - x86/retbleed: Add fine grained Kconfig knobs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#f43b9876</link>
        <description>x86/retbleed: Add fine grained Kconfig knobsDo fine-grained Kconfig for all the various retbleed parts.NOTE: if your compiler doesn&apos;t support return thunks this willsilently &apos;upgrade&apos; your mitigation to IBPB, you might not like this.Signed-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Mon, 27 Jun 2022 22:21:17 +0000</pubDate>
        <dc:creator>Peter Zijlstra &lt;peterz@infradead.org&gt;</dc:creator>
    </item>
<item>
        <title>a09a6e23 - objtool: Add entry UNRET validation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#a09a6e23</link>
        <description>objtool: Add entry UNRET validationSince entry asm is tricky, add a validation pass that ensures theretbleed mitigation has been done before the first actual RETinstruction.Entry points are those that either have UNWIND_HINT_ENTRY, which actsas UNWIND_HINT_EMPTY but marks the instruction as an entry point, orthose that have UWIND_HINT_IRET_REGS at +0.This is basically a variant of validate_branch() that isintra-function and it will simply follow all branches from markedentry points and ensures that all paths lead to ANNOTATE_UNRET_END.If a path hits RET or an indirection the path is a fail and will bereported.There are 3 ANNOTATE_UNRET_END instances: - UNTRAIN_RET itself - exception from-kernel; this path doesn&apos;t need UNTRAIN_RET - all early exceptions; these also don&apos;t need UNTRAIN_RETSigned-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;Reviewed-by: Josh Poimboeuf &lt;jpoimboe@kernel.org&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Tue, 14 Jun 2022 21:16:03 +0000</pubDate>
        <dc:creator>Peter Zijlstra &lt;peterz@infradead.org&gt;</dc:creator>
    </item>
<item>
        <title>b42d2306 - kbuild: factor out the common objtool arguments</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#b42d2306</link>
        <description>kbuild: factor out the common objtool argumentsscripts/Makefile.build and scripts/link-vmlinux.sh have similar setupsfor the objtool arguments.It was difficult to factor out them because all the vmlinux build ruleswere written in a shell script. It is somewhat tedious to touch the twofiles every time a new objtool option is supported.To reduce the code duplication, move the objtool for vmlinux.o intoscripts/Makefile.vmlinux_o. Then, move the common macros to Makefile.libso they are shared between Makefile.build and Makefile.vmlinux_o.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Sedat Dilek &lt;sedat.dilek@gmail.com&gt; # LLVM-14 (x86-64)

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Sat, 28 May 2022 15:47:04 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5d45950d - kbuild: move vmlinux.o link to scripts/Makefile.vmlinux_o</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/Makefile.vmlinux_o#5d45950d</link>
        <description>kbuild: move vmlinux.o link to scripts/Makefile.vmlinux_oThis is a preparation for moving the objtool rule in the next commit.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Sedat Dilek &lt;sedat.dilek@gmail.com&gt; # LLVM-14 (x86-64)

            List of files:
            /linux-6.15/scripts/Makefile.vmlinux_o</description>
        <pubDate>Sat, 28 May 2022 15:47:03 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
