<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/s390/kernel/vdso64, branch linux-6.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2025-02-21T08:54:02Z</updated>
<entry>
<title>s390/vdso: Switch to generic storage implementation</title>
<updated>2025-02-21T08:54:02Z</updated>
<author>
<name>Thomas Weißschuh</name>
</author>
<published>2025-02-04T12:05:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9bf39a65b20cd03b10c618b1b1c4703538a5b564'/>
<id>urn:sha1:9bf39a65b20cd03b10c618b1b1c4703538a5b564</id>
<content type='text'>
The generic storage implementation provides the same features as the
custom one. However it can be shared between architectures, making
maintenance easier.

Co-developed-by: Nam Cao &lt;namcao@linutronix.de&gt;
Signed-off-by: Nam Cao &lt;namcao@linutronix.de&gt;
Signed-off-by: Thomas Weißschuh &lt;thomas.weissschuh@linutronix.de&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Link: https://lore.kernel.org/all/20250204-vdso-store-rng-v3-12-13a4669dfc8c@linutronix.de

</content>
</entry>
<entry>
<title>vdso: Rename included Makefile</title>
<updated>2025-02-21T08:54:01Z</updated>
<author>
<name>Thomas Weißschuh</name>
</author>
<published>2025-02-04T12:05:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=127b0e05c1669d240426719b3b9db8a8366eed50'/>
<id>urn:sha1:127b0e05c1669d240426719b3b9db8a8366eed50</id>
<content type='text'>
As the Makefile is included into other Makefiles it can not be used to
define objects to be built from the current source directory.
However the generic datastore will introduce such a local source file.
Rename the included Makefile so it is clear how it is to be used and to
make room for a regular Makefile in lib/vdso/.

Signed-off-by: Thomas Weißschuh &lt;thomas.weissschuh@linutronix.de&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Link: https://lore.kernel.org/all/20250204-vdso-store-rng-v3-4-13a4669dfc8c@linutronix.de

</content>
</entry>
<entry>
<title>s390/Kconfig: Select VMAP_STACK unconditionally</title>
<updated>2024-12-10T14:41:58Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2024-12-02T11:56:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=27939d6cde904bcea19d0cdb64a79eedf5abc7ce'/>
<id>urn:sha1:27939d6cde904bcea19d0cdb64a79eedf5abc7ce</id>
<content type='text'>
There is no point in supporting !VMAP_STACK kernel builds. VMAP_STACK has
proven to work since many years. Also, since KASAN_VMALLOC is supported,
kernels built with !VMAP_STACK are completely untested.

Therefore select VMAP_STACK unconditionally and remove all config options
and code required for !VMAP_STACK builds.

Acked-by: Christian Borntraeger &lt;borntraeger@linux.ibm.com&gt;
Reviewed-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Signed-off-by: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Drop LBASE_VDSO</title>
<updated>2024-11-02T11:37:32Z</updated>
<author>
<name>Thomas Weißschuh</name>
</author>
<published>2024-10-10T07:01:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=98333a84e3318a1dd08a3ec6def98abfb8215cdb'/>
<id>urn:sha1:98333a84e3318a1dd08a3ec6def98abfb8215cdb</id>
<content type='text'>
This constant is always "0", providing no value and making the logic
harder to understand.
Also prepare for a consolidation of the vdso linkerscript logic by
aligning it with other architectures.

Signed-off-by: Thomas Weißschuh &lt;thomas.weissschuh@linutronix.de&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Link: https://lore.kernel.org/all/20241010-vdso-generic-base-v1-3-b64f0842d512@linutronix.de

</content>
</entry>
<entry>
<title>s390/vdso: Use one large alternative instead of an alternative branch</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2024-09-19T12:40:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d714abee5fb64c4817dce477bd7f2bd1bb4fe814'/>
<id>urn:sha1:d714abee5fb64c4817dce477bd7f2bd1bb4fe814</id>
<content type='text'>
Replace the alternative branch with a larger alternative that contains
both paths. That way the two paths are closer together and it is easier
to change both paths if the need should arise.

Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Reviewed-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Use SYM_DATA_START_LOCAL()/SYM_DATA_END() for data objects</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2024-09-19T12:40:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c902b578eebfe0739e8ec491b60f2f37dfeb09c0'/>
<id>urn:sha1:c902b578eebfe0739e8ec491b60f2f37dfeb09c0</id>
<content type='text'>
Use SYM_DATA_START_LOCAL()/SYM_DATA_END() in vgetrandom-chacha.S so
that the constants end up in an object with correct size:

readelf -Ws vgetrandom-chacha.o
   Num:    Value          Size Type    Bind   Vis      Ndx Name
   ...
     5: 0000000000000000    32 OBJECT  LOCAL  DEFAULT    5 chacha20_constants

Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Reviewed-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Use macros for annotation of asm functions</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Jens Remus</name>
</author>
<published>2024-09-19T12:40:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d361390d9f2a332b52458cc69f1fe8e76d6c2943'/>
<id>urn:sha1:d361390d9f2a332b52458cc69f1fe8e76d6c2943</id>
<content type='text'>
Use the macros SYM_FUNC_START() and SYM_FUNC_END() to annotate the
functions in assembly.

Signed-off-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Acked-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Add CFI annotations to __arch_chacha20_blocks_nostack()</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Jens Remus</name>
</author>
<published>2024-09-19T12:40:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5cccfc8be6d256e91d155313edef20c1a89064b2'/>
<id>urn:sha1:5cccfc8be6d256e91d155313edef20c1a89064b2</id>
<content type='text'>
This allows proper unwinding, for instance when using a debugger such
as GDB.

Signed-off-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Acked-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Fix comment within __arch_chacha20_blocks_nostack()</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2024-09-19T12:40:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ff35a3f0ca5c88145c6da6630f3420071dfa296c'/>
<id>urn:sha1:ff35a3f0ca5c88145c6da6630f3420071dfa296c</id>
<content type='text'>
Fix comment within __arch_chacha20_blocks_nostack() so the comment
reflects what the code is doing.

Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Reviewed-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>s390/vdso: Get rid of permutation constants</title>
<updated>2024-09-23T15:57:04Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2024-09-19T12:40:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8e391ae0607fc820e9ece87d1415e6a1ff274e69'/>
<id>urn:sha1:8e391ae0607fc820e9ece87d1415e6a1ff274e69</id>
<content type='text'>
The three byte masks for VECTOR PERMUTE are not needed, since the
instruction VECTOR SHIFT LEFT DOUBLE BY BYTE can be used to implement
the required "rotate left" easily.

Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;
Reviewed-by: Jens Remus &lt;jremus@linux.ibm.com&gt;
Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;
</content>
</entry>
</feed>
