cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: cip-dev@lists.cip-project.org
Cc: Chris Paterson <Chris.Paterson2@renesas.com>
Subject: Re: [cip-dev] Kselftest implementation
Date: Thu, 22 Apr 2021 16:34:55 +0900	[thread overview]
Message-ID: <20210422073455.cygkkkglll4fuv24@toshiba.co.jp> (raw)
In-Reply-To: <CANgtXuNS0S6G2sdYdxX4272kXfDp63MYXOeLFtSW3+kcrYQ0AQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4122 bytes --]

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, 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.

> 
> 
> > 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?

> 
> >
> > >
> > > linux-cip Kernel Kselftest implementation (currently in draft):
> > > https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/merge_requests
> >
> > Please assign the MR to me when you're ready for it to be reviewed, or if
> > you need any help.
> >
> > Also let me know if you want write access to the linux-cip-ci repo.
> > If you push your branch to our repo directly the CI will be able to run,
> > making it easier for you to test.
> >
> 
> Testing the kselftest branch directly on CIP CI test environment from
> linux-cip-ci
> repo would be really helpful.
> 
> Thanks,
> Alicef


Best regards,
  Nobuhiro

[-- Attachment #2: Type: text/plain, Size: 428 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6383): https://lists.cip-project.org/g/cip-dev/message/6383
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]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2021-04-22  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 17:29 [cip-dev] Kselftest implementation Alice Ferrazzi
2021-04-13 22:27 ` Chris Paterson
2021-04-15  2:04   ` Alice Ferrazzi
2021-04-22  7:34     ` Nobuhiro Iwamatsu [this message]
2021-04-23  8:49       ` Alice Ferrazzi

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=20210422073455.cygkkkglll4fuv24@toshiba.co.jp \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.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 NNTP newsgroup(s).