From: "Thomas Weißschuh" <linux@weissschuh.net>
To: David Gow <david@davidgow.net>
Cc: Michal Simek <monstr@monstr.eu>,
Brendan Higgins <brendan.higgins@linux.dev>,
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: Wed, 5 Aug 2026 21:18:30 +0200 [thread overview]
Message-ID: <e11bc960-b31c-408a-a57e-631e76806bb5@t-8ch.de> (raw)
In-Reply-To: <42dfe558-f75b-4d7c-a560-449101bae4f5@davidgow.net>
On 2026-08-05 21:59:16+0800, David Gow wrote:
> Le 04/08/2026 à 13:32, Thomas Weißschuh a écrit :
> > Add a basic configuration to run kunit tests on microblaze.
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
>
> Works well here, though there are still a couple of test failures (and a
> longer timeout is needed to get through them all on my machine):
>
> > Testing complete. Ran 965 tests: passed: 866, failed: 3, skipped: 96
> > Failures: blake2s.test_hash_alignment_consistency,
> memcpy.memmove_overlap_test, printf.dentry
These are all due to the broken memmove() implementation.
It should be fixed by *either*:
- Disabling CONFIG_OPT_LIB_FUNCTION
- Enabling CONFIG_OPT_LIB_ASM
> I'm okay with this going in via either the microblaze or KUnit trees. Any
> preferences?
None from me. I would have expected it to go through microblaze, though.
> Reviewed-by: David Gow <david@davidgow.net>
Thanks!
(...)
next prev parent reply other threads:[~2026-08-05 19:18 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 [this message]
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
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=e11bc960-b31c-408a-a57e-631e76806bb5@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=monstr@monstr.eu \
--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