[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a305c732-9953-8724-b4a4-25aa50c89365@gmail.com>
Date: Tue, 14 May 2019 17:26:47 -0700
From: Frank Rowand <frowand.list@...il.com>
To: Theodore Ts'o <tytso@....edu>, Tim.Bird@...y.com,
knut.omang@...cle.com, gregkh@...uxfoundation.org,
brendanhiggins@...gle.com, keescook@...gle.com,
kieran.bingham@...asonboard.com, mcgrof@...nel.org,
robh@...nel.org, sboyd@...nel.org, shuah@...nel.org,
devicetree@...r.kernel.org, dri-devel@...ts.freedesktop.org,
kunit-dev@...glegroups.com, linux-doc@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-um@...ts.infradead.org,
Alexander.Levin@...rosoft.com, amir73il@...il.com,
dan.carpenter@...cle.com, dan.j.williams@...el.com,
daniel@...ll.ch, jdike@...toit.com, joel@....id.au,
julia.lawall@...6.fr, khilman@...libre.com, logang@...tatee.com,
mpe@...erman.id.au, pmladek@...e.com, richard@....at,
rientjes@...gle.com, rostedt@...dmis.org, wfg@...ux.intel.com
Subject: Re: [PATCH v2 00/17] kunit: introduce KUnit, the Linux kernel unit
testing framework
On 5/11/19 10:33 AM, Theodore Ts'o wrote:
> On Fri, May 10, 2019 at 02:12:40PM -0700, Frank Rowand wrote:
>> However, the reply is incorrect. Kselftest in-kernel tests (which
>> is the context here) can be configured as built in instead of as
>> a module, and built in a UML kernel. The UML kernel can boot,
>> running the in-kernel tests before UML attempts to invoke the
>> init process.
>
> Um, Citation needed?
The paragraph that you quoted tells you exactly how to run a kselftest
in-kernel test in a UML kernel. Just to what that paragraph says.
>
> I don't see any evidence for this in the kselftest documentation, nor
> do I see any evidence of this in the kselftest Makefiles.
>
> There exists test modules in the kernel that run before the init
> scripts run --- but that's not strictly speaking part of kselftests,
> and do not have any kind of infrastructure. As noted, the
> kselftests_harness header file fundamentally assumes that you are
> running test code in userspace.
You are ignoring the kselftest in-kernel tests.
We are talking in circles. I'm done with this thread.
-Frank
>
> - Ted
> .
>
Powered by blists - more mailing lists