Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Michal Simek <michal.simek@amd.com>
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
	 David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>,
	linux-kernel@vger.kernel.org,  linux-kselftest@vger.kernel.org,
	kunit-dev@googlegroups.com
Subject: Re: [PATCH 4/4] kunit: qemu_configs: Add microblaze configuration
Date: Tue, 1 Sep 2026 20:33:39 +0200	[thread overview]
Message-ID: <b48fee3e-d113-4551-aed4-100a089e33b5@t-8ch.de> (raw)
In-Reply-To: <40f679a2-fb5d-4d69-96dd-ab6c6718ac07@amd.com>

On 2026-09-01 15:33:11+0200, Michal Simek wrote:
> On 8/31/26 17:43, Thomas Weißschuh wrote:
> > On 2026-08-31 12:48:08+0200, Michal Simek wrote:

(...)

> > > If there is an issue with memmove implementation I can't see any issue to
> > > disable that options to let it pass from the beginning and solve it
> > > separately.
> > 
> > Ack. Could you take care of this? I have next to no idea about microblaze.
> 
> On little endian this is passing. I can add it to my todo list but big
> endian is very very old and likely none is using it anymore.

If it is not supposed to work maybe mark it as BROKEN or disable the
custom memmove() implementation there and instead rely on the generic
one from lib/string.c?

> > 
> > > This should be fragment for Little endian.
> > 
> > Thanks, unfortunately this hangs for me with my distros QEMU 11.1.0.
> > No output, 100% CPU usage during boot. I am using qemu-system-microblaze
> > instead of qemu-system-microblazel, as the latter is not available
> > anymore, but the former is documented to also handle little endian
> > automatically.
> > 
> 
> I built the latest qemu like this
> 
> ../qemu/configure --target-list=microblaze-softmmu,microblaze-linux-user,microblazeel-linux-user
> --enable-gcrypt --disable-docs
> 
> /mnt/projects/xilinx-new-git/qemu.org/build-microblaze/qemu-system-microblaze
> --version
> QEMU emulator version 11.1.50 (v11.1.0-779-gd2e570cc0f97)

For me it still doesn't work. I am using the same build of QEMU and GCC
13.4.0 (or 16.2.0) from crosstools.kernel.org.

> And can't see any issue.

(...)

> /mnt/projects/xilinx-new-git/qemu.org/build-microblaze/qemu-system-microblaze
> -nodefaults -m 1024 -kernel .kunit/arch/microblaze/boot/linux.bin -append
> 'kunit.enable=1 kunit_shutdown=poweroff' -no-reboot -nographic -accel kvm
> -accel hvf -accel tcg -serial stdio -M petalogix-ml605
> qemu-system-microblaze: -accel kvm: invalid accelerator kvm
> qemu-system-microblaze: -accel hvf: invalid accelerator hvf
> qemu-system-microblaze: falling back to tcg
> qemu-system-microblaze: warning: nic xlnx.axi-ethernet.0 has no peer
> random: crng init done
> Ramdisk addr 0x00000000,
> FDT at 0x5058e528
> Linux version 7.3.0-rc1-00023-g5a713478d535 (monstr@monstr-desktop3)
> (microblazeel-amd-linux-gcc.real (GCC) 13.4.0, GNU ld (GNU Binutils)

I guess this is a special GCC variant. Could you try with one from
https://mirrors.edge.kernel.org/pub/tools/crosstool/ ?

(...)


Thomas

  reply	other threads:[~2026-09-01 18:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  5:32 [PATCH 0/4] microblaze: KUnit support Thomas Weißschuh
2026-08-04  5:32 ` [PATCH 1/4] microblaze: uaccess: Zero out destination on failed get_user() Thomas Weißschuh
2026-08-05 13:59   ` David Gow
2026-08-04  5:32 ` [PATCH 2/4] microblaze: reset: Call POWER_OFF handlers Thomas Weißschuh
2026-08-05 13:59   ` David Gow
2026-08-31  8:13   ` Michal Simek
2026-08-31 15:39     ` Thomas Weißschuh
2026-08-04  5:32 ` [PATCH 3/4] microblaze: reset: Provide a power off handler through an unaligned PC Thomas Weißschuh
2026-08-05 13:59   ` David Gow
2026-08-04  5:32 ` [PATCH 4/4] kunit: qemu_configs: Add microblaze configuration Thomas Weißschuh
2026-08-05 13:59   ` David Gow
2026-08-05 19:18     ` Thomas Weißschuh
2026-08-31  8:15       ` Michal Simek
2026-08-31 10:48   ` Michal Simek
2026-08-31 15:43     ` Thomas Weißschuh
2026-09-01 13:33       ` Michal Simek
2026-09-01 18:33         ` Thomas Weißschuh [this message]
2026-09-02 10:44           ` Michal Simek
2026-08-31 12:57 ` [PATCH 0/4] microblaze: KUnit support Michal Simek
2026-08-31 15:45   ` Thomas Weißschuh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b48fee3e-d113-4551-aed4-100a089e33b5@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=brendan.higgins@linux.dev \
    --cc=david@davidgow.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=raemoar63@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox