[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181207010517.GH28501@garbanzo.do-not-panic.com>
Date: Thu, 6 Dec 2018 17:05:17 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Kieran Bingham <kieran.bingham@...asonboard.com>
Cc: Brendan Higgins <brendanhiggins@...gle.com>,
Kent Overstreet <kent.overstreet@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Eryu Guan <guaneryu@...il.com>,
Eric Sandeen <sandeen@...deen.net>, jeffm@...e.com,
Sasha Levin <Alexander.Levin@...rosoft.com>,
Greg KH <gregkh@...uxfoundation.org>,
Kees Cook <keescook@...gle.com>, shuah@...nel.org,
Joel Stanley <joel@....id.au>, mpe@...erman.id.au,
joe@...ches.com, brakmo@...com, rostedt@...dmis.org,
Tim.Bird@...y.com, khilman@...libre.com,
Julia Lawall <julia.lawall@...6.fr>,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jdike@...toit.com, richard@....at, linux-um@...ts.infradead.org,
Daniel Vetter <daniel@...ll.ch>,
dri-devel@...ts.freedesktop.org, Rob Herring <robh@...nel.org>,
dan.j.williams@...el.com, linux-nvdimm@...ts.01.org,
Frank Rowand <frowand.list@...il.com>,
Knut Omang <knut.omang@...cle.com>,
Felix Guo <felixguoxiuping@...il.com>,
Petr Mladek <pmladek@...e.com>, fsdevel@...r.kernel.org
Subject: Re: [RFC v3 11/19] kunit: add Python libraries for handing KUnit
config and kernel
On Thu, Dec 06, 2018 at 12:32:47PM +0000, Kieran Bingham wrote:
> My main initial idea for a libumlinux is to provide infrastructure such
> as our linked-lists and other kernel formatting so that we can take
> kernel code directly to userspace for test and debug (assuming that
> there are no hardware dependencies or things that we can't mock out)
The tools/ directory already does this for a tons of things. Its where
I ended up placing some API I tested a long time ago when I wanted to
test it in userspace, and provide the unit test in userspace (for my
linker table patches).
> Now we just have to start the race to see who can tweak the kernel build
> system to produce an output library first :)
Should be relatively easy if the tools directory used. Yes, there is
an inherent risk of duplication, but that was decided long ago.
Luis
Powered by blists - more mailing lists