linux-kernel - Re: [PATCH] tools/nolibc: Add m68k support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250426065613.GA8661@1wt.eu>
Date: Sat, 26 Apr 2025 08:56:13 +0200
From: Willy Tarreau <w@....eu>
To: Daniel Palmer <daniel@...f.com>
Cc: linux@...ssschuh.net, linux-m68k@...r.kernel.org, geert@...ux-m68k.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/nolibc: Add m68k support

On Sat, Apr 26, 2025 at 03:16:35PM +0900, Daniel Palmer wrote:
> Hi Willy,
> 
> On Sat, 26 Apr 2025 at 14:14, Willy Tarreau <w@....eu> wrote:
> > Nice, thank you! Could you please also add support for it to
> > tools/testing/selftests/nolibc/ and verify that it works ?
> 
> Sure, doing that now. For now it'll be using the mmu enabled m68k virt
> machine that QEMU supports out of the box.

Ah, I didn't know that there's both mmu and nommu for m68k :-)

> > changes. You may possible have to add a few ifndef, as I don't
> > think we've ever had a nommu platform yet. If you face too many
> > failures or just difficulties, please let us know so that we can
> > figure together a suitable solution.
> 
> I need to test actually building and running something for nommu but I
> will do that later today.
> Making nommu test automatically might be a bit difficult though as I
> think it only really works with some changes I have to linux and QEMU.

OK no worries, my point really is that it's important to implement the
test for the target platform. If it's mmu only that's fine, as it will
ensure we don't break it in future updates.

thanks,
Willy