From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NORMAL_HTTP_TO_IP,NUMERIC_HTTP_ADDR,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,WEIRD_PORT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C5E37C433B4 for ; Fri, 23 Apr 2021 08:49:46 +0000 (UTC) Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7DEAD6141C for ; Fri, 23 Apr 2021 08:49:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7DEAD6141C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=miraclelinux.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=bounce+64572+6385+4520388+8129055@lists.cip-project.org X-Received: by 127.0.0.2 with SMTP id 50tmYY4521723x1mgbIJt3kx; Fri, 23 Apr 2021 01:49:43 -0700 X-Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) by mx.groups.io with SMTP id smtpd.web10.7036.1619167781313663514 for ; Fri, 23 Apr 2021 01:49:43 -0700 X-Received: by mail-ed1-f53.google.com with SMTP id z5so20095279edr.11 for ; Fri, 23 Apr 2021 01:49:41 -0700 (PDT) X-Gm-Message-State: Sg5WYqmrDnex8wJIDUfDHTCfx4520388AA= X-Google-Smtp-Source: ABdhPJz3NG844qJYreuxqKo5MxINt2EeTGBtKChYB6v2oYdv1tjTLyo/Tyz3SrZaWBPUE70Hvrp7F/GqilnD+BFtzu4= X-Received: by 2002:aa7:dd4d:: with SMTP id o13mr3227039edw.53.1619167779647; Fri, 23 Apr 2021 01:49:39 -0700 (PDT) MIME-Version: 1.0 References: <20210422073455.cygkkkglll4fuv24@toshiba.co.jp> In-Reply-To: <20210422073455.cygkkkglll4fuv24@toshiba.co.jp> From: "Alice Ferrazzi" Date: Fri, 23 Apr 2021 17:49:03 +0900 Message-ID: Subject: Re: [cip-dev] Kselftest implementation To: cip-dev@lists.cip-project.org Precedence: Bulk List-Unsubscribe: List-Subscribe: List-Help: Sender: cip-dev@lists.cip-project.org List-Id: Mailing-List: list cip-dev@lists.cip-project.org; contact cip-dev+owner@lists.cip-project.org Reply-To: cip-dev@lists.cip-project.org Content-Type: multipart/mixed; boundary="7f8qMEcdYw2E1eAvyznn" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.cip-project.org; q=dns/txt; s=20140610; t=1619167783; bh=tCCTehysJaHg7V69wkl6r/hvMe/MHhKPyHizz/BTbTs=; h=Content-Type:Date:From:Reply-To:Subject:To; b=wkUySun4PXEZlhWJRA3C19PyNkVaCQ4gIpAYRWWMdwNJZmw0iAGcOKiIpJhZ3uQCrL3 u3kqvRqaEmqzkDXcj577wSfPsMrZCGSgXygZvzPWQZ+fHhprjNldV+P47FL7ScDq06VC+ gA4J4bfp0G+lb2G4VdADG0kLoYgp5z082pg= --7f8qMEcdYw2E1eAvyznn Content-Type: multipart/alternative; boundary="0000000000005686a905c09fe067" --0000000000005686a905c09fe067 Content-Type: text/plain; charset="UTF-8" Hi, thanks for the review, On Thu, Apr 22, 2021 at 4:35 PM Nobuhiro Iwamatsu < nobuhiro1.iwamatsu@toshiba.co.jp> wrote: > Hi, > > Thanks for your work. > > On Thu, Apr 15, 2021 at 11:04:26AM +0900, Alice Ferrazzi wrote: > > Hello Chris, > > > > On Wed, Apr 14, 2021 at 7:27 AM Chris Paterson < > Chris.Paterson2@renesas.com> > > wrote: > > > > > Hello Alice, > > > > > > > From: cip-dev@lists.cip-project.org > On > > > > Behalf Of Alice Ferrazzi via lists.cip-project.org > > > > Sent: 13 April 2021 18:30 > > > > > > > > Hi everyone, > > > > > > > > I'm Alice Ferrazzi from Cybertrust Japan. > > > > > > > > I'm currently working on adding Kselftest to the current CIP CI > tests of > > > linux- > > > > cip Kernel > > > > > > Thank you for your work on this! > > > > > > > > > > > I made and tested kselftest on a testing instance of lava, currently > > > tested > > > > only on qemu x86_64 > > > > > > If you'd like to test on a wider range of platforms then get in touch > and > > > we'll get you access to the CIP LAVA instance. > > > > > > > This would be nice! > > > > > > > > I implemented a simple skiplist in the kselftest envelope for > skipping > > > tests > > > > that are currently not working. > > > > The usage is similar to how spectre-meltdown-checker-test is > currently > > > > working. > > > > > > > > Raw log: > > > > > > > > http://140.211.166.173:10080/scheduler/job/329 > > > > Results list: > > > > http://140.211.166.173:10080/results/329/1_kselftest > > > > > > It looks like a great start. > > > > > > > > Thanks > > > > > > > > > > > > > My idea is to start implementing kselftest tests for at least qemu > x86_64 > > > > architecture and expand in the future to other architectures. > > > > As Iwamatsu-san pointed, we need also to create kselftest binary. > > > > > > > > I'm currently thinking of implementing kselftest binary creation > > > mechanism > > > > on linux-cip-ci kernel build script but I still didn't start to work > on > > > this yet. > > > > > > > > Kselftest test code: > > > > > > > > https://gitlab.com/alice.ferrazzi/cip-kselftest > > > > > > > > Is there any work we can leverage from the Linaro test-definitions repo? > > > > > > > https://github.com/Linaro/test-definitions/tree/master/automated/linux/kselftest > > > > > > That was the first thing I tried out but was not working correctly on > the > > cip rootfs enviroment > > As you write, cip rootfs lacks the software to run kselftest. Therefore, > it is necessary to make a separate flavor of rootfs. > There are also two types of cip rootfs, and we need to use either or > both for kernel testing. > ok. > > > > > > > KernelCI also recently implemented kselftest support if that's useful > at > > > all, this'll include the build side of things. > > > > https://github.com/kernelci/kernelci-core/tree/main/config/lava/kselftest > > > > > > > > I know about KernelCI effort for kselftest and I think to use a similar > > approach about the kselftest binary creation implementation. > > > > The code I wrote is based on Glava-tests that is part of GKernelCI. > > GKernelCI is the current Gentoo kernel CI system that is reporting and > > collaborating with KernelCI. > > https://github.com/GKernelCI/Glava-tests > > Using a different repository currently is helpful for self managing the > > skiplist, but it could be changed in the future. > > > I think this needs to be done first. > I also think there are several approaches to creating kselftest > binaries. > > - Continue to use a particular kernel version of ksefltests. > - Use CIP kernel kselftest. > - Use the latest kernel kselftest. > > I used to build an environment using the latter. > > > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/tree/ci/iwamatsu/linux-cip-kselftest > > By the way, do you know which kernelci they are using? > KernelCI is using a docker container for building kselftest https://github.com/kernelci/kernelci-core/blob/26924e6b1a90833bcdf8eb28d038fa2fac19885f/config/docker/gcc-8_x86/Dockerfile KernelCI is building kselftest in production for at least linux-next and mainline any time a new revision is discovered on the branches. on staging.kernelci.org kselftest is built for each job. This was yesterday staging build with kselftest https://staging.kernelci.org/build/kernelci/branch/staging-mainline/kernel/staging-mainline-20210422.0/ Currently I'm working on a similar implementation for CIP testing. Thanks, Alicef -- ====================================== Cybertrust Japan Co.,Ltd. Alice Ferrazzi alice.ferrazzi@miraclelinux.com ====================================== --0000000000005686a905c09fe067 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
= Hi,

<= /div>
thanks for= the review,


On Thu, Apr 22, 2021 at 4:35 PM Nobuhiro I= wamatsu <nobuhiro1.iwamatsu@toshiba.co.jp> wrote:
Hi,

Thanks for your work.

On Thu, Apr 15, 2021 at 11:04:26AM +0900, Alice Ferrazzi wrote:
> Hello Chris,
>
> On Wed, Apr 14, 2021 at 7:27 AM Chris Paterson <Chris.Paterson2@renesas.com>
> wrote:
>
> > Hello Alice,
> >
> > > From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> > > Behalf Of Alice Ferrazzi via lists.cip-project.org > > > Sent: 13 April 2021 18:30
> > >
> > > Hi everyone,
> > >
> > > I'm Alice Ferrazzi from Cybertrust Japan.
> > >
> > > I'm currently working on adding Kselftest to the current= CIP CI tests of
> > linux-
> > > cip Kernel
> >
> > Thank you for your work on this!
> >
> > >
> > > I made and tested kselftest on a testing instance of lava, c= urrently
> > tested
> > > only on qemu x86_64
> >
> > If you'd like to test on a wider range of platforms then get = in touch and
> > we'll get you access to the CIP LAVA instance.
> >
>
> This would be nice!
>
>
> > > I implemented a simple skiplist in the kselftest envelope fo= r skipping
> > tests
> > > that are currently not working.
> > > The usage is similar to how spectre-meltdown-checker-test is= currently
> > > working.
> > >
> > > Raw log:
> > >
> > > http://140.211.166.173:10080/scheduler/= job/329
> > > Results list:
> > > http://140.211.166.173:10080/resu= lts/329/1_kselftest
> >
> > It looks like a great start.
> >
> >
> Thanks
>
> >
> > >
> > > My idea is to start implementing kselftest tests for at leas= t qemu x86_64
> > > architecture and expand in the future to other architectures= .
> > > As Iwamatsu-san pointed, we need also to create kselftest bi= nary.
> > >
> > > I'm currently thinking of implementing kselftest binary = creation
> > mechanism
> > > on linux-cip-ci kernel build script but I still didn't s= tart to work on
> > this yet.
> > >
> > > Kselftest test code:
> > >
> > > https://gitlab.com/alice.ferrazzi/cip-= kselftest
> >
> >
> Is there any work we can leverage from the Linaro test-definitions rep= o?
> >
> > https://gi= thub.com/Linaro/test-definitions/tree/master/automated/linux/kselftest<= br> > >
> > That was the first thing I tried out but was not working correctl= y on the
> cip rootfs enviroment

As you write, cip rootfs lacks the software to run kselftest. Therefore, it is necessary to make a separate flavor of rootfs.
There are also two types of cip rootfs, and we need to use either or
both for kernel testing.
=C2=A0

ok.

=C2=A0
>
>
> > KernelCI also recently implemented kselftest support if that'= s useful at
> > all, this'll include the build side of things.
> > https://github.co= m/kernelci/kernelci-core/tree/main/config/lava/kselftest
> >
> >
> I know about KernelCI effort for kselftest and I think to use a simila= r
> approach about the kselftest binary creation implementation.
>
> The code I wrote is based on Glava-tests that is part of GKernelCI. > GKernelCI is the current Gentoo kernel CI system that is reporting and=
> collaborating with KernelCI.
> https://github.com/GKernelCI/Glava-tests
> Using a different repository currently is helpful for self managing th= e
> skiplist, but it could be changed in the future.


I think this needs to be done first.
I also think there are several approaches to creating kselftest
binaries.

- Continue to use a particular kernel version of ksefltests.
- Use CIP kernel kselftest.
- Use the latest kernel kselftest.

I used to build an environment using the latter.

https://gi= tlab.com/cip-project/cip-kernel/linux-cip/-/tree/ci/iwamatsu/linux-cip-ksel= ftest

By the way, do you know which kernelci they are using?

Kern= elCI is using a docker container for building kselftest
https://gith= ub.com/kernelci/kernelci-core/blob/26924e6b1a90833bcdf8eb28d038fa2fac19885f= /config/docker/gcc-8_x86/Dockerfile

KernelCI is building kselftest in production for at leas= t linux-next and mainline any time a new revision is discovered on the bran= ches. on staging.= kernelci.org kselftest is built for each job.
This was yesterday staging build with ks= elftest
http= s://staging.kernelci.org/build/kernelci/branch/staging-mainline/kernel/stag= ing-mainline-20210422.0/

Currently I'm working on a similar implementation for CIP testing.<= /div>

Thanks,
Alicef



--
=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
Cybertrust Japan Co.,Ltd.
Alice Ferra= zzi
alice.ferrazzi@miraclelinux.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
--0000000000005686a905c09fe067-- --7f8qMEcdYw2E1eAvyznn Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Links: You receive all messages sent to this group. View/Reply Online (#6385): https://lists.cip-project.org/g/cip-dev/message= /6385 Mute This Topic: https://lists.cip-project.org/mt/82071182/4520388 Group Owner: cip-dev+owner@lists.cip-project.org Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388= /727948398/xyzzy [cip-dev@archiver.kernel.org] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --7f8qMEcdYw2E1eAvyznn--