From: Knut Omang <knut.omang@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
Shuah Khan <shuah@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Shreyans Devendra Doshi <0xinfosect0r@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>,
Brendan Higgins <brendanhiggins@google.com>,
Kevin Hilman <khilman@baylibre.com>,
Hidenori Yamaji <hidenori.yamaji@sony.com>,
Frank Rowand <frowand.list@gmail.com>,
Timothy Bird <Tim.Bird@sony.com>,
Luis Chamberlain <mcgrof@kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>, Daniel Vetter <daniel@ffwll.ch>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [RFC 00/19] Integration of Kernel Test Framework (KTF) into the kernel tree
Date: Tue, 13 Aug 2019 11:51:05 +0200 [thread overview]
Message-ID: <f0e1a6efa8f21ab93935c4c19e13b904d4a71f98.camel@oracle.com> (raw)
In-Reply-To: <20190813082336.GB17627@kroah.com>
On Tue, 2019-08-13 at 10:23 +0200, Greg Kroah-Hartman wrote:
> On Tue, Aug 13, 2019 at 08:09:15AM +0200, Knut Omang wrote:
> > and in the making::
> >
> > kunit/ (kernel only (UML))
>
> You are going to have to integrate this with kunit, to come up with a
> superset of both in the end.
Yes, I agree - getting to a unified approach has been my intention since I first brought this
up at LPC'17.
> And I do not think that kunit is only UML, it's just that seems to be
> what Brendan tests with, but should work with other arches as well.
If I get Brendan right, it is UML only now but can be extended to also support
kernels running on real hardware. Still it is kernel only, while KTF also has the
hybrid mode, where a test can have code and assertions both in user mode and kernel mode.
This is made easier and more streamlined by letting all reporting happen from user mode.
Thanks!
Knut
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2019-08-13 9:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 6:09 [RFC 00/19] Integration of Kernel Test Framework (KTF) into the kernel tree Knut Omang
2019-08-13 6:09 ` [RFC 01/19] kbuild: Fixes to rules for host-cshlib and host-cxxshlib Knut Omang
2019-08-13 14:01 ` Masahiro Yamada
2019-08-13 16:19 ` Knut Omang
2019-08-14 2:02 ` Masahiro Yamada
2019-08-14 5:50 ` Knut Omang
2019-08-14 5:52 ` Knut Omang
2019-08-14 12:52 ` Knut Omang
2019-08-21 1:47 ` Masahiro Yamada
2019-08-21 4:03 ` Knut Omang
2019-08-13 6:09 ` [RFC 02/19] ktf: Introduce the main part of the kernel side of ktf Knut Omang
2019-09-09 1:23 ` Brendan Higgins
2019-09-10 6:15 ` Knut Omang
2019-08-13 6:09 ` [RFC 03/19] ktf: Introduce a generic netlink protocol for test result communication Knut Omang
2019-09-09 1:28 ` Brendan Higgins
2019-09-10 6:30 ` Knut Omang
2019-08-13 6:09 ` [RFC 04/19] ktf: An implementation of a generic associative array container Knut Omang
2019-08-13 6:09 ` [RFC 05/19] ktf: Implementation of ktf support for overriding function entry and return Knut Omang
2019-08-13 6:09 ` [RFC 06/19] ktf: A simple debugfs interface to test results Knut Omang
2019-08-13 8:21 ` Greg Kroah-Hartman
2019-08-14 17:17 ` Knut Omang
2019-08-15 8:49 ` Greg Kroah-Hartman
2019-08-15 10:35 ` Knut Omang
2019-08-15 10:52 ` Greg Kroah-Hartman
2019-08-13 6:09 ` [RFC 07/19] ktf: Simple coverage support Knut Omang
2019-08-13 6:09 ` [RFC 08/19] ktf: Configurable context support for network info setup Knut Omang
2019-08-13 6:09 ` [RFC 09/19] ktf: resolve: A helper utility to aid in exposing private kernel symbols to KTF tests Knut Omang
2019-08-13 6:09 ` [RFC 10/19] ktf: Add documentation for Kernel Test Framework (KTF) Knut Omang
2019-08-13 6:09 ` [RFC 11/19] ktf: Add a small test suite with a few tests to test KTF itself Knut Omang
2019-08-13 6:09 ` [RFC 12/19] ktf: Main part of user land library for executing tests Knut Omang
2019-08-13 6:09 ` [RFC 13/19] ktf: Integration logic for running ktf tests from googletest Knut Omang
2019-08-13 6:09 ` [RFC 14/19] ktf: Internal debugging facilities Knut Omang
2019-08-13 6:09 ` [RFC 15/19] ktf: Some simple examples Knut Omang
2019-08-13 6:09 ` [RFC 16/19] ktf: Some user applications to run tests Knut Omang
2019-08-13 6:09 ` [RFC 17/19] ktf: Toplevel ktf Makefile/makefile includes and scripts to run from kselftest Knut Omang
2019-08-13 6:09 ` [RFC 18/19] kselftests: Enable building ktf Knut Omang
2019-08-13 6:09 ` [RFC 19/19] Documentation/dev-tools: Add index entry for KTF documentation Knut Omang
2019-08-13 8:10 ` [RFC 00/19] Integration of Kernel Test Framework (KTF) into the kernel tree Brendan Higgins
2019-08-13 8:17 ` Brendan Higgins
2019-08-13 11:29 ` Knut Omang
2019-08-13 17:50 ` Brendan Higgins
2019-08-13 8:23 ` Greg Kroah-Hartman
2019-08-13 9:51 ` Knut Omang [this message]
2019-08-13 17:02 ` Brendan Higgins
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=f0e1a6efa8f21ab93935c4c19e13b904d4a71f98.camel@oracle.com \
--to=knut.omang@oracle.com \
--cc=0xinfosect0r@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=alan.maguire@oracle.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hidenori.yamaji@sony.com \
--cc=khilman@baylibre.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=sboyd@kernel.org \
--cc=shuah@kernel.org \
--cc=tytso@mit.edu \
--cc=yamada.masahiro@socionext.com \
/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).