<?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>68b9883c - um: Discover host_task_size from envp</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/um/os-Linux/Makefile#68b9883c</link>
        <description>um: Discover host_task_size from envpWhen loading the UML binary, the host kernel will place the stack at thehighest possible address. It will then map the program name andenvironment variables onto the start of the stack.As such, an easy way to figure out the host_task_size is to use thehighest pointer to an environment variable as a reference.Ensure that this works by disabling address layout randomization andre-executing UML in case it was enabled.This increases the available TASK_SIZE for 64 bit UML considerably.Signed-off-by: Benjamin Berg &lt;benjamin.berg@intel.com&gt;Link: https://patch.msgid.link/20240919124511.282088-9-benjamin@sipsolutions.netSigned-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;

            List of files:
            /linux-6.15/arch/x86/um/os-Linux/Makefile</description>
        <pubDate>Thu, 19 Sep 2024 12:45:09 +0000</pubDate>
        <dc:creator>Benjamin Berg &lt;benjamin.berg@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>1ca14435 - um: Rely on PTRACE_SETREGSET to set FS/GS base registers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/um/os-Linux/Makefile#1ca14435</link>
        <description>um: Rely on PTRACE_SETREGSET to set FS/GS base registersThese registers are saved/restored together with the other generalregisters using ptrace. In arch_set_tls we then just need to set theregister and it will be synced back normally.Most of this logic was introduced in commit f355559cf7845 (&quot;[PATCH] uml:x86_64 thread fixes&quot;). However, at least today we can rely on ptrace torestore the base registers for us. As such, only the part of the patchthat tracks the FS register for use as thread local storage is actuallyneeded.Signed-off-by: Benjamin Berg &lt;benjamin@sipsolutions.net&gt;Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;

            List of files:
            /linux-6.15/arch/x86/um/os-Linux/Makefile</description>
        <pubDate>Fri, 10 Nov 2023 11:03:46 +0000</pubDate>
        <dc:creator>Benjamin Berg &lt;benjamin@sipsolutions.net&gt;</dc:creator>
    </item>
<item>
        <title>67d7c302 - kbuild: remove --include-dir MAKEFLAG from top Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/um/os-Linux/Makefile#67d7c302</link>
        <description>kbuild: remove --include-dir MAKEFLAG from top MakefileI added $(srctree)/ to some included Makefiles in the following commits: - 3204a7fb98a3 (&quot;kbuild: prefix $(srctree)/ to some included Makefiles&quot;) - d82856395505 (&quot;kbuild: do not require sub-make for separate output tree builds&quot;)They were a preparation for removing --include-dir flag.I have never thought --include-dir useful. Rather, it _is_ harmful.For example, run the following commands:  $ make -s ARCH=x86 mrproper defconfig  $ make ARCH=arm O=foo dtbs  make[1]: Entering directory &apos;/tmp/linux/foo&apos;    HOSTCC  scripts/basic/fixdep  Error: kernelrelease not valid - run &apos;make prepare&apos; to update it    UPD     include/config/kernel.release  make[1]: Leaving directory &apos;/tmp/linux/foo&apos;The first command configures the source tree for x86. The next commandtries to build ARM device trees in the separate foo/ directory - thismust stop because the directory foo/ has not been configured yet.However, due to --include-dir=$(abs_srctree), the top Makefile includesthe wrong include/config/auto.conf from the source tree and continuesbuilding. Kbuild traverses the directory tree, but of course it doesnot work correctly. The Error message is also pointless - &apos;make prepare&apos;does not help at all for fixing the issue.This commit fixes more arch Makefile, and finally removes --include-dirfrom the top Makefile.There are more breakages under drivers/, but I do not volunteer to fixthem all. I just moved --include-dir to drivers/Makefile.With this commit, the second command will stop with a sensible message.  $ make -s ARCH=x86 mrproper defconfig  $ make ARCH=arm O=foo dtbs  make[1]: Entering directory &apos;/tmp/linux/foo&apos;    SYNC    include/config/auto.conf.cmd  ***  *** The source tree is not clean, please run &apos;make ARCH=arm mrproper&apos;  *** in /tmp/linux  ***  make[2]: *** [../Makefile:646: outputmakefile] Error 1  /tmp/linux/Makefile:770: include/config/auto.conf.cmd: No such file or directory  make[1]: *** [/tmp/linux/Makefile:793: include/config/auto.conf.cmd] Error 2  make[1]: Leaving directory &apos;/tmp/linux/foo&apos;  make: *** [Makefile:226: __sub-make] Error 2Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/arch/x86/um/os-Linux/Makefile</description>
        <pubDate>Sat, 28 Jan 2023 09:24:23 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5c48b108 - um: take arch/um/sys-x86 to arch/x86/um</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/um/os-Linux/Makefile#5c48b108</link>
        <description>um: take arch/um/sys-x86 to arch/x86/umSigned-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;

            List of files:
            /linux-6.15/arch/x86/um/os-Linux/Makefile</description>
        <pubDate>Thu, 18 Aug 2011 19:06:39 +0000</pubDate>
        <dc:creator>Al Viro &lt;viro@ftp.linux.org.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
