<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/tools/testing/selftests/bpf/config.ppc64el, branch linux-rolling-stable</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-rolling-stable</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-rolling-stable'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2025-08-26T11:47:03Z</updated>
<entry>
<title>selftests/bpf: Remove entries from config.{arch} already present in config</title>
<updated>2025-08-26T11:47:03Z</updated>
<author>
<name>Tiezhu Yang</name>
<email>yangtiezhu@loongson.cn</email>
</author>
<published>2025-08-26T06:50:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d0f27ff27c048a3bdc49877255a7e7f8b49f5603'/>
<id>urn:sha1:d0f27ff27c048a3bdc49877255a7e7f8b49f5603</id>
<content type='text'>
`config.{arch}` had entries already present in `config`.

When generating the config used by vmtest, concatenate the `config` file
with the `config.{arch}` one, making those entries duplicated, so remove
those duplications.

Use the following command to get the differences:

  $ comm -1 -2  &lt;(sort tools/testing/selftests/bpf/config.x86_64) &lt;(sort tools/testing/selftests/bpf/config)
  $ comm -1 -2  &lt;(sort tools/testing/selftests/bpf/config.aarch64) &lt;(sort tools/testing/selftests/bpf/config)
  $ comm -1 -2  &lt;(sort tools/testing/selftests/bpf/config.riscv64) &lt;(sort tools/testing/selftests/bpf/config)
  $ comm -1 -2  &lt;(sort tools/testing/selftests/bpf/config.ppc64el) &lt;(sort tools/testing/selftests/bpf/config)
  $ comm -1 -2  &lt;(sort tools/testing/selftests/bpf/config.s390x) &lt;(sort tools/testing/selftests/bpf/config)

This is similar with commit 7a42af4b94f1 ("selftests/bpf: Remove entries
from config.s390x already present in config").

Signed-off-by: Tiezhu Yang &lt;yangtiezhu@loongson.cn&gt;
Signed-off-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Link: https://lore.kernel.org/bpf/20250826065057.11415-1-yangtiezhu@loongson.cn
</content>
</entry>
<entry>
<title>selftests/bpf: Support ppc64el in vmtest</title>
<updated>2025-06-23T16:34:58Z</updated>
<author>
<name>Luis Gerhorst</name>
<email>luis.gerhorst@fau.de</email>
</author>
<published>2025-06-19T14:08:53Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=3ce7cdde66e65a400b2d1b2a7f72c499e1db26b6'/>
<id>urn:sha1:3ce7cdde66e65a400b2d1b2a7f72c499e1db26b6</id>
<content type='text'>
With a rootfs built using libbpf's BPF CI [1], we can run specific tests
as follows:

$ ../libbpf-ci/rootfs/mkrootfs_debian.sh --arch ppc64el --distro noble
$ PLATFORM=ppc64el CROSS_COMPILE=powerpc64le-linux-gnu- \
    tools/testing/selftests/bpf/vmtest.sh \
    -l libbpf-vmtest-rootfs-*-noble-ppc64el.tar.zst \
    -- ./test_progs -t verifier_array_access

Does not include a DENYLIST or support for KVM for now.

[1] https://github.com/libbpf/ci

Signed-off-by: Luis Gerhorst &lt;luis.gerhorst@fau.de&gt;
Link: https://lore.kernel.org/r/20250619140854.2135283-1-luis.gerhorst@fau.de
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
</feed>
