From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: Guo Ren <guoren@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 4/5] tools/nolibc: add csky support
Date: Mon, 30 Sep 2024 07:23:39 +0200 [thread overview]
Message-ID: <2f4a244d-e88c-4378-8b1b-71204964dab6@t-8ch.de> (raw)
In-Reply-To: <20240930034946.GB13730@1wt.eu>
Hi Willy,
On 2024-09-30 05:49:46+0000, Willy Tarreau wrote:
> 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].
[2] was supposed to be inline patches for QEMU, I'll try to make that a
bit clearer.
> > 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.
As mentioned above, these are patches for qemu, not Linux.
I don't know enough about QEMU or C-SKY to know if these are the
generally correct fixes. But they seem to work well enough for nolibc.
Guo, if these QEMU patches look reasonable to you I can also submit them.
> 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 ;-)
Agreed!
Thomas
next prev parent reply other threads:[~2024-09-30 5:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 21:47 [PATCH 0/5] csky: add shutdown and nolibc support Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 1/5] drivers/virt: introduce csky_exit system poweroff driver Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 2/5] tools/nolibc: provide a fallback for lseek through llseek Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 3/5] selftests/nolibc: add support to use standalone kernels for tests Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 4/5] tools/nolibc: add csky support Thomas Weißschuh
2024-09-30 3:49 ` Willy Tarreau
2024-09-30 5:23 ` Thomas Weißschuh [this message]
2024-09-30 6:04 ` Willy Tarreau
2024-09-29 21:47 ` [PATCH 5/5] selftests/nolibc: skip test for getppid() on csky 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=2f4a244d-e88c-4378-8b1b-71204964dab6@t-8ch.de \
--to=linux@weissschuh.net \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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