<?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 vdso</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6eda706a - selftests: vDSO: fix the way vDSO functions are called for powerpc</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#6eda706a</link>
        <description>selftests: vDSO: fix the way vDSO functions are called for powerpcvdso_test_correctness test fails on powerpc:~ # ./vdso_test_correctness...[RUN]	Testing clock_gettime for clock CLOCK_REALTIME_ALARM (8)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22[RUN]	Testing clock_gettime for clock CLOCK_BOOTTIME_ALARM (9)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22[RUN]	Testing clock_gettime for clock CLOCK_SGI_CYCLE (10)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22...[RUN]	Testing clock_gettime for clock invalid (-1)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22[RUN]	Testing clock_gettime for clock invalid (-2147483648)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22[RUN]	Testing clock_gettime for clock invalid (2147483647)...[FAIL]	No such clock, but __vdso_clock_gettime returned 22On powerpc, a call to a VDSO function is not an ordinary C functioncall. Unlike several architectures which returns a negative error codein case of an error, powerpc sets CR[SO] and returns the error codeas a positive value.Define and use a macro called VDSO_CALL() which takes a pointerto the function to call, the number of arguments and the arguments.Also update ABI vdso documentation to reflect this subtlety.Provide a specific version of VDSO_CALL() for powerpc that negatesthe error code on return when CR[SO] is set.Fixes: c7e5789b24d3 (&quot;kselftest: Move test_vdso to the vDSO test suite&quot;)Fixes: 2e9a97256616 (&quot;selftests: vdso: Add a selftest for vDSO getcpu()&quot;)Fixes: 693f5ca08ca0 (&quot;kselftest: Extend vDSO selftest&quot;)Fixes: b2f1c3db2887 (&quot;kselftest: Extend vdso correctness test to clock_gettime64&quot;)Fixes: 4920a2590e91 (&quot;selftests/vDSO: add tests for vgetrandom&quot;)Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Acked-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Fri, 30 Aug 2024 12:28:38 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>97f26cab - docs: ABI: vdso: use the right format for ABI</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#97f26cab</link>
        <description>docs: ABI: vdso: use the right format for ABIThis ABI is not following the format described at ABI/README.Use it, filling in the blanks with the git log that added it,and using the current e-mail from Andy.Acked-by: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/28c7cf3a71e15fb7499b70ec8f38c2efaaf4add2.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Fri, 30 Oct 2020 07:40:48 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>98913408 - docs: ABI: stable: make files ReST compatible</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#98913408</link>
        <description>docs: ABI: stable: make files ReST compatibleSeveral entries at the stable ABI files won&apos;t parse if we passthem directly to the ReST output.Adjust them, in order to allow adding their contents as-is atthe stable ABI book.Acked-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;Acked-by: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/467a0dfbcdf00db710a629d3fe4a2563750339d8.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Fri, 30 Oct 2020 07:40:38 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>904d94f0 - doc: ABI: vdso: update parse_vdso.c reference</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#904d94f0</link>
        <description>doc: ABI: vdso: update parse_vdso.c referenceSince commit f9b6b0ef603 (&quot;selftests: move vDSO tests from Documentation/vDSO&quot;)parse_vdso.c moved under selftests. Update the reference to match.Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Baruch Siach &lt;baruch@tkos.co.il&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Wed, 08 Mar 2017 19:50:31 +0000</pubDate>
        <dc:creator>Baruch Siach &lt;baruch@tkos.co.il&gt;</dc:creator>
    </item>
<item>
        <title>79980d9c - [media] Documentation: Add newline at end-of-file to files lacking one</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#79980d9c</link>
        <description>[media] Documentation: Add newline at end-of-file to files lacking oneThis patch simply adds a newline character at end-of-file to thosefiles in Documentation/ that currently lack one.This is done for a few different reasons:A) It&apos;s rather annoying when you do &quot;cat some_file.txt&quot; that your   prompt/cursor ends up at the end of the last line of output rather   than on a new line.B) Some tools that process files line-by-line may get confused by the   lack of a newline on the last line.C) The &quot;\ No newline at end of file&quot; line in diffs annoys me for some   reason.So, let&apos;s just add the missing newline once and for all.Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Fri, 20 Jul 2012 19:35:17 +0000</pubDate>
        <dc:creator>Jesper Juhl &lt;jj@chaosbits.net&gt;</dc:creator>
    </item>
<item>
        <title>f9028317 - Documentation: Add newline at end-of-file to files lacking one</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#f9028317</link>
        <description>Documentation: Add newline at end-of-file to files lacking oneThis patch simply adds a newline character at end-of-file to thosefiles in Documentation/ that currently lack one.This is done for a few different reasons:A) It&apos;s rather annoying when you do &quot;cat some_file.txt&quot; that your   prompt/cursor ends up at the end of the last line of output rather   than on a new line.B) Some tools that process files line-by-line may get confused by the   lack of a newline on the last line.C) The &quot;\ No newline at end of file&quot; line in diffs annoys me for some   reason.So, let&apos;s just add the missing newline once and for all.Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Fri, 20 Jul 2012 20:35:17 +0000</pubDate>
        <dc:creator>Jesper Juhl &lt;jj@chaosbits.net&gt;</dc:creator>
    </item>
<item>
        <title>98eedc3a - Document the vDSO and add a reference parser</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/stable/vdso#98eedc3a</link>
        <description>Document the vDSO and add a reference parserIt turns out that parsing the vDSO is nontrivial if you don&apos;t alreadyhave an ELF dynamic loader around.  So document it in Documentation/ABIand add a reference CC0-licenced parser.This code is dedicated to Go issue 1933:http://code.google.com/p/go/issues/detail?id=1933Signed-off-by: Andy Lutomirski &lt;luto@mit.edu&gt;Link: http://lkml.kernel.org/r/a315a9514cd71bcf29436cc31e35aada21a5ff21.1310563276.git.luto@mit.eduSigned-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;

            List of files:
            /linux-6.15/Documentation/ABI/stable/vdso</description>
        <pubDate>Wed, 13 Jul 2011 13:24:16 +0000</pubDate>
        <dc:creator>Andy Lutomirski &lt;luto@mit.edu&gt;</dc:creator>
    </item>
</channel>
</rss>
