linux-kernel - Re: [RFC PATCH v3 00/37] Upstream kvx Linux port

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: <8648033e-6eb5-42f7-a65d-3153992e9135@kalrayinc.com>
Date: Thu, 25 Jul 2024 12:07:38 +0200
From: Yann Sionneau <ysionneau@...rayinc.com>
To: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Cc: Jonathan Borne <jborne@...rayinc.com>, Julian Vetter
 <jvetter@...rayinc.com>, Paul Iannetta <piannetta@...ray.eu>, Xavier Raynaud
 <xraynaud@...ray.eu>, Patrice GERIN <pgerin@...ray.eu>
Subject: Re: [RFC PATCH v3 00/37] Upstream kvx Linux port

Hello Arnd,

Le 7/24/24 à 09:59, Arnd Bergmann a écrit :
> On Mon, Jul 22, 2024, at 11:41, ysionneau@...rayinc.com wrote:
>> From: Yann Sionneau <ysionneau@...rayinc.com>
>>
>> This patch series adds support for the kv3-1 CPU architecture of the kvx family
>> found in the Coolidge (aka MPPA3-80) SoC of Kalray.
> Thanks for posting it again. I tried to read through it
> and point out a few things I noticed. It's been a while
> since v2, so I may have forgotten things we already discussed.
>
> I did not see any major issues here, the main things that
> take work to implement (better atomics, vmemmap, also vmap_stack
> which I did not mention) are just there to make your code
> better, but are not required to get it merged.
Thanks a lot for your reviews, as always it's much appreciated.
>> This is an RFC, since kvx support is not yet upstreamed into gcc,
>> therefore this patch series cannot be merged into Linux for now.
> Do you have a timeline for upstream compiler support?  I see that
> your github trees contain both llvm and gcc forks on an older
> baseline (gcc-12.2 and llvm-15, respectively), but I don't know
> how much you have already submitting for inclusion in a newer
> release.
We are still willing to contribute our kvx support into upstream gcc, 
but we cannot commit to a deadline yet because

of some code cleanup that is needed and we don't have a date for it yet.

We also do have public gcc 13.2.0 support 
(https://github.com/kalray/gcc/blob/coolidge/ChangeLog) and llvm 15.0.7

We regularly (every 3 months) push on our github repos updated toolchains.

As said in the cover letter binutils kvx support is now upstream.

Regards,

-- 

Yann