public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Tom Gall" <tom.gall@linaro.org>
To: kernelci@groups.io
Subject: kernelci, functional testing and Android
Date: Mon, 19 Nov 2018 14:15:03 -0800	[thread overview]
Message-ID: <16817.1542665703675183029@groups.io> (raw)

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

One of the things that we do today within Linaro through LKFT is validate LTS+AndroidCommon kernels on a set of boards utilizing Android as the host operating system as well as a subset of CTS and VTS which are two automated test suites. Works pretty well and has the benefit putting the kernel through a good battery of tests. As with anything, it's not perfect, etc etc. 

There is a bit more than a passing interest to boot Android on mainline kernels [0]  and as that starts to happen that this could allow for some amount of Linux kernel validation utilizing Android with KernelCI in the future. I think this is a good goal to strive for and would be complementary to functional testing efforts on Linux. It's what we do already within Linaro in LKFT after all through something called Project Sharp [1]. I suspect there's a number of things that would need to be worked out to make that happen, but that's the point of the email, understand what's problematic, how one might start to kick the tires and seeing if anyone else is interested. 

The kernelci.org FAQ doesn't have much about getting started, so forgive me if I didn't look in an obvious place I should have.

Thanks!
Tom 

[0] - https://lwn.net/Articles/771974/
[1] - https://elciotna18.sched.com/event/DXnC/keeping-up-with-lts-linux-kernel-functional-testing-lkft-on-devices-thomas-gall-linaro

[-- Attachment #2: Type: text/html, Size: 1450 bytes --]

                 reply	other threads:[~2018-11-19 22:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=16817.1542665703675183029@groups.io \
    --to=tom.gall@linaro.org \
    --cc=kernelci@groups.io \
    /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