On 2026-08-31 14:57:36+0200, Michal Simek wrote:
> Hi,
> 
> On 8/4/26 07:32, Thomas Weißschuh wrote:
> > Add the necessary prerequisites and configuration to run KUnit on
> > microblaze.
> > 
> > Please note that various KUnit tests will fail with the default
> > configuration as the memmove() implementation from
> > arch/microblaze/lib/memmove.c seems to be broken.
> > 
> > Signed-off-by: Thomas Weißschuh <[email protected]>
> > ---
> > Thomas Weißschuh (4):
> >        microblaze: uaccess: Zero out destination on failed get_user()
> >        microblaze: reset: Call POWER_OFF handlers
> >        microblaze: reset: Provide a power off handler through an unaligned 
> > PC
> >        kunit: qemu_configs: Add microblaze configuration
> > 
> >   arch/microblaze/Kconfig                        |  9 +++++++++
> >   arch/microblaze/include/asm/uaccess.h          |  3 ++-
> >   arch/microblaze/kernel/reset.c                 | 22 ++++++++++++++++++++++
> >   tools/testing/kunit/qemu_configs/microblaze.py | 17 +++++++++++++++++
> >   4 files changed, 50 insertions(+), 1 deletion(-)
> > ---
> > base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
> > change-id: 20260802-kunit-microblaze-7a3f6ac88b4d
> > 
> > Best regards,
> > --
> > Thomas Weißschuh <[email protected]>
> > 
> 
> One more thing. I see that this test is also failing on 32bit riscv. Is this
> something 32bit architecture related? That was only one test which failed on
> little endian Microblaze.

This is a general issue of this test on 32-bit:
https://lore.kernel.org/lkml/[email protected]/

(...)

> [14:53:56]     # gpu_test_buddy_alloc_exceeds_max_order:
> drivers/gpu/buddy.c:519: gpu_buddy_assert(!mm->used_scoreboard[i])
> [14:53:56] [FAILED] gpu_test_buddy_alloc_exceeds_max_order
> [14:53:56] # gpu_buddy: Testing GPU buddy manager, with random_seed=0x11376afa
> [14:53:56] # module: gpu_buddy_tests
> [14:53:56] ==================== [FAILED] gpu_buddy ====================
> [14:53:56] ============================================================
> [14:53:56] Testing complete. Ran 1 tests: failed: 1
> [14:53:56] Elapsed time: 6.310s total, 0.001s configuring, 4.289s building,
> 1.982s running

Reply via email to