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: <20240930034946.GB13730@1wt.eu>
Date: Mon, 30 Sep 2024 05:49:46 +0200
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Guo Ren <guoren@...nel.org>, Shuah Khan <shuah@...nel.org>,
        linux-kernel@...r.kernel.org, linux-csky@...r.kernel.org,
        linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 4/5] tools/nolibc: add csky support

Hi Thomas,

On Sun, Sep 29, 2024 at 11:47:39PM +0200, Thomas Weißschuh wrote:
> Add support for the C-SKY architecture, which is very similar to
> LoongArch.
> Only v2 ABI is supported.
> Optimizations are disabled as the compiler[0] seems to misoptimize the
> code, especially the r4 register gets clobbered.
> Compile the initramfs directly into the kernel, as qemu does not support
> passing the initrd via OF.
> 
> There is no qemu mainline support for qemu.
> Testing was done with commit 1f172a2c7cd5c2e7 of the downstream csky qemu [1].
> Some tiny changes were necessary on top [2].
> 
> [0] gcc 13.2.0 and 14.2.0 from kernel.org crosstools
> [1] https://github.com/XUANTIE-RV/qemu/
> [2]

I think you wanted to place a link or something above for [2].

> diff --git a/target/csky/cpu-param.h b/target/csky/cpu-param.h
> index 80554cc0fc03..9181b602a26f 100644
> --- a/target/csky/cpu-param.h
> +++ b/target/csky/cpu-param.h
(...)
> diff --git a/target/csky/op_vdsp2.c b/target/csky/op_vdsp2.c
> index a9985a03be33..d953f5ea94fe 100644
> --- a/target/csky/op_vdsp2.c
> +++ b/target/csky/op_vdsp2.c

Also, the first two patches look like fixes for the arch itself, they
should really go outside of the nolibc development tree, at least
because they might have to be backported to some stable branches,
or later fixed/reverted in case they wouldn't be optimal.

Aside this, it's been a long time since we last added an architecture
and it's pleasant to see how easy it has become over time, even when
requiring specific settings ;-)

Cheers,
Willy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ