From: Alexandre Ghiti <alex@ghiti.fr>
To: Donald Zickus <dzickus@redhat.com>, Gustavo Padovan <gus@collabora.com>
Cc: kernelci <kernelci@lists.linux.dev>,
"Rafael Sene" <rafael@riscv.org>,
"Helen koike" <helen.koike@collabora.com>,
"Björn Töpel" <bjorn@rivosinc.com>
Subject: Re: RISC-V
Date: Mon, 14 Oct 2024 13:05:58 +0200 [thread overview]
Message-ID: <578c7c03-1252-47e5-996b-73048383dfc2@ghiti.fr> (raw)
In-Reply-To: <CAK18DXbgQcBhia8na9Nn8taTuXtJkJ1d2AvnXO_hELk9wMUSqw@mail.gmail.com>
Hi Gustavo, Donald,
On 01/10/2024 18:36, Donald Zickus wrote:
> Hi Alexandre,
>
> On Tue, Oct 1, 2024 at 12:31 PM Gustavo Padovan <gus@collabora.com> wrote:
>>
>> Hi Alexandre,
>>
>> ---- On Tue, 01 Oct 2024 12:21:49 -0300 Alexandre Ghiti wrote ---
>>
>> > Hi everyone,
>> >
>> > We (the RISC-V community) are looking for improving our CIs that are
>> > currently spread over all the RISC-V companies, mostly private and very
>> > incomplete.
>>
>> That is great to hear! We have other hardware vendors coming to KernelCI with the same wishes of improving CI overall.
>>
>> >
>> > I only found one RISC-V build in kernelci, can I do something to help
>> > adding a better RISC-V support?
>>
>> YES!
>>
>> First of all, we can enable more kernel trees and kernel configs in the maestro system.
>> That would give you wider build coverage. If you have a list of configs we can work on adding these.
>> - https://docs.kernelci.org/kernel-community/
>>
>> Then, we have to look at running these kernel on actual RISC-V devices. We can get RISC-V devices in KernelCI through a maestro lab, either through some of the existing labs or setting up a dedicated lab. Cc'ing Rafael from RISC-V as we discussed that already.
>> - https://docs.kernelci.org/labs/
>>
>> Another way, that could be relatively easy if you have a CI setup already, is to get the results of the current CIs in the RISC-V ecosystem into KCIDB (as long as you area running fully Open Source software in those tests).
>> - https://docs.kernelci.org/kcidb/
>>
>> Let us know how does that sound to you. We would happy to learn more about the ways we can make this work and chat more with you.
> In addition to everything Gustavo mentioned above, Red Hat's Fedora
> project can be another path as it uses CKI to do some CI testing and
> submit results to the same KCIDB mentioned above. I believe Red Hat
> already has folks in the RISC-V community working on getting the
> hardware enabled on Fedora and possibly RHEL. Just another option.
> Either way works or both!
>
> Cheers,
> Don
>
>> Best,
>>
>> - Gus
>>
>>
Sorry for the late answer! Bjorn and I have been talking with Rafael and
we'll soon come up with a plan to integrate RISC-V in KernelCI, I'll
keep you posted :)
Thanks again for your quick answers,
Alex
prev parent reply other threads:[~2024-10-14 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 15:21 RISC-V Alexandre Ghiti
2024-10-01 16:17 ` RISC-V Gustavo Padovan
2024-10-01 16:36 ` RISC-V Donald Zickus
2024-10-14 11:05 ` Alexandre Ghiti [this message]
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=578c7c03-1252-47e5-996b-73048383dfc2@ghiti.fr \
--to=alex@ghiti.fr \
--cc=bjorn@rivosinc.com \
--cc=dzickus@redhat.com \
--cc=gus@collabora.com \
--cc=helen.koike@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=rafael@riscv.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).