[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g45VsXEXX--z-tjZWOTLgodnUwnOgyGqJVgy4xbz_YZFTQ@mail.gmail.com>
Date: Tue, 3 Dec 2019 15:06:17 -0800
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Alan Maguire <alan.maguire@...cle.com>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
KUnit Development <kunit-dev@...glegroups.com>,
Kees Cook <keescook@...omium.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
catalin.marinas@....com, joe.lawrence@...hat.com,
penguin-kernel@...ove.sakura.ne.jp, urezki@...il.com,
andriy.shevchenko@...ux.intel.com,
Jonathan Corbet <corbet@....net>,
David Gow <davidgow@...gle.com>, adilger.kernel@...ger.ca,
"Theodore Ts'o" <tytso@....edu>,
Luis Chamberlain <mcgrof@...nel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v5 linux-kselftest-test 0/6] kunit: support building
core/tests as modules
On Tue, Dec 3, 2019 at 4:08 AM Alan Maguire <alan.maguire@...cle.com> wrote:
>
> The current kunit execution model is to provide base kunit functionality
> and tests built-in to the kernel. The aim of this series is to allow
> building kunit itself and tests as modules. This in turn allows a
> simple form of selective execution; load the module you wish to test.
> In doing so, kunit itself (if also built as a module) will be loaded as
> an implicit dependency.
>
> Because this requires a core API modification - if a module delivers
> multiple suites, they must be declared with the kunit_test_suites()
> macro - we're proposing this patch set as a candidate to be applied to the
> test tree before too many kunit consumers appear. We attempt to deal
> with existing consumers in patch 3.
Tested-by: Brendan Higgins <brendanhiggins@...gle.com>
Powered by blists - more mailing lists