linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	Lawrence Brakmo <brakmo@fb.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Sasha Levin <Alexander.Levin@microsoft.com>,
	linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	linux-nvdimm@lists.01.org, Richard Weinberger <richard@nod.at>,
	knut.omang@oracle.com,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Joel Stanley <joel@jms.id.au>, Jeff Dike <jdike@addtoit.com>,
	"Bird, Timothy" <Tim.Bird@sony.com>,
	Kees Cook <keescook@google.com>,
	linux-um@lists.infradead.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	levinsasha928@gmail.com, Dan Williams <dan.j.williams@intel.com>,
	kunit-dev@googlegroups.com, gregkh <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel@ffwll.ch>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Joe Perches <joe@perches.com>,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: [RFC v3 01/19] kunit: test: add KUnit test runner core
Date: Wed, 5 Dec 2018 14:49:10 +0000	[thread overview]
Message-ID: <5bd5581f-f192-4ed0-6f5f-9e1bf9f443e2@cambridgegreys.com> (raw)
In-Reply-To: <CAK8P3a2HrOTYv7qCJH1XGVxZ2HDqwkHqRWaAJ93nWc5p8LnCig@mail.gmail.com>

On 05/12/2018 14:45, Arnd Bergmann wrote:
> On Wed, Dec 5, 2018 at 2:42 PM Anton Ivanov
> <anton.ivanov@cambridgegreys.com> wrote:
>> On 30/11/2018 03:14, Luis Chamberlain wrote:
>>> On Wed, Nov 28, 2018 at 11:36:18AM -0800, Brendan Higgins wrote:
>>> Then for the UML stuff, I think if we *really* accept that UML will
>>> always be a viable option we should probably consider now throwing these
>>> things under drivers/platform/uml/. This follows the pattern of arch
>>> specific drivers. Whether or not we end up with a complete userspace
>> UML platform drivers predate that and are under arch/um/drivers/
>>
>> We should either keep to current convention or consider relocating the
>> existing ones - having things spread in different places around the tree
>> is not good in the long run (UML already has a few of those under the
>> x86 tree, let's not increase the number).
> I don't mind the current location much, but if we move drivers, we should
> move the into the appropriate subsystems based on what they do, rather
> than having a new place with a mix of things.
>
> E.g. the tty drivers should all be in drivers/tty/ and the network drivers in
> drivers/net. To paraphrase what you said above: having tty drivers spread in
> different places around the tree is not good in the long run. We have long
> ago moved from organizing drivers by bus interface to organizing drivers
> by class, uml and drivers/platform are just exceptions to this rule.

There are some issues with that because uml drivers have bits of what is 
effectively host side of the hypervisor as a part of them. IMHO, having 
that in driver/X is not very appropriate. So at least the *_user.c and 
*_user.h bits have to go (or stay) somewhere else

Brgds,

-- 
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661


  reply	other threads:[~2018-12-05 14:49 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 19:36 [RFC v3 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework Brendan Higgins
2018-11-28 19:36 ` [RFC v3 01/19] kunit: test: add KUnit test runner core Brendan Higgins
2018-11-30  3:14   ` Luis Chamberlain
2018-12-01  1:51     ` Brendan Higgins
2018-12-01  2:57       ` Luis Chamberlain
2018-12-05 13:15     ` Anton Ivanov
2018-12-05 14:45       ` Arnd Bergmann
2018-12-05 14:49         ` Anton Ivanov [this message]
2018-11-30  3:28   ` Luis Chamberlain
2018-12-01  2:08     ` Brendan Higgins
2018-12-01  3:10       ` Luis Chamberlain
2018-12-03 22:47         ` Brendan Higgins
2018-12-01  3:02   ` Luis Chamberlain
2018-11-28 19:36 ` [RFC v3 02/19] kunit: test: add test resource management API Brendan Higgins
2018-11-28 19:36 ` [RFC v3 03/19] kunit: test: add string_stream a std::stream like string builder Brendan Higgins
2018-11-30  3:29   ` Luis Chamberlain
2018-12-01  2:14     ` Brendan Higgins
2018-12-01  3:12       ` Luis Chamberlain
2018-12-03 10:55     ` Petr Mladek
2018-12-04  0:35       ` Brendan Higgins
2018-11-28 19:36 ` [RFC v3 04/19] kunit: test: add test_stream a std::stream like logger Brendan Higgins
2018-11-28 19:36 ` [RFC v3 05/19] kunit: test: add the concept of expectations Brendan Higgins
2018-11-28 19:36 ` [RFC v3 06/19] arch: um: enable running kunit from User Mode Linux Brendan Higgins
2018-11-28 21:26   ` Rob Herring
2018-11-30  3:37     ` Luis Chamberlain
2018-11-30 14:05       ` Rob Herring
2018-11-30 18:22         ` Luis Chamberlain
2018-12-03 23:22           ` Brendan Higgins
2018-11-30  3:30   ` Luis Chamberlain
2018-11-28 19:36 ` [RFC v3 07/19] kunit: test: add initial tests Brendan Higgins
2018-11-30  3:40   ` Luis Chamberlain
2018-12-03 23:26     ` Brendan Higgins
2018-12-03 23:43       ` Luis Chamberlain
2018-11-28 19:36 ` [RFC v3 08/19] arch: um: add shim to trap to allow installing a fault catcher for tests Brendan Higgins
2018-11-30  3:34   ` Luis Chamberlain
2018-12-03 23:34     ` Brendan Higgins
2018-12-03 23:46       ` Luis Chamberlain
2018-12-04  0:44         ` Brendan Higgins
2018-11-30  3:41   ` Luis Chamberlain
2018-12-03 23:37     ` Brendan Higgins
2018-11-28 19:36 ` [RFC v3 09/19] kunit: test: add the concept of assertions Brendan Higgins
2018-11-28 19:36 ` [RFC v3 10/19] kunit: test: add test managed resource tests Brendan Higgins
2018-11-28 19:36 ` [RFC v3 11/19] kunit: add Python libraries for handing KUnit config and kernel Brendan Higgins
2018-11-29 13:54   ` Kieran Bingham
2018-12-03 23:48     ` Brendan Higgins
2018-12-04 20:47       ` Luis Chamberlain
2018-12-06 12:32         ` Kieran Bingham
2018-12-06 15:37           ` Matthew Wilcox
2018-12-07 11:30             ` Kieran Bingham
2018-12-11 14:09             ` Petr Mladek
2018-12-11 14:41               ` Steven Rostedt
2018-12-11 17:01                 ` Anton Ivanov
2019-02-09  0:40                   ` Brendan Higgins
2018-12-07  1:05           ` Luis Chamberlain
2018-12-07 18:35           ` Kent Overstreet
2018-11-30  3:44   ` Luis Chamberlain
2018-12-03 23:50     ` Brendan Higgins
2018-12-04 20:48       ` Luis Chamberlain
2018-11-28 19:36 ` [RFC v3 12/19] kunit: add KUnit wrapper script and simple output parser Brendan Higgins
2018-11-28 19:36 ` [RFC v3 13/19] kunit: improve output from python wrapper Brendan Higgins
2018-11-28 19:36 ` [RFC v3 14/19] Documentation: kunit: add documentation for KUnit Brendan Higgins
2018-11-29 13:56   ` Kieran Bingham
2018-11-30  3:45     ` Luis Chamberlain
2018-12-03 23:53       ` Brendan Higgins
2018-12-06 12:16         ` Kieran Bingham
2019-02-09  0:56           ` Brendan Higgins
2019-02-11 12:16             ` Kieran Bingham
2019-02-12 22:10               ` Brendan Higgins
2019-02-13 21:55                 ` Kieran Bingham
2019-02-14  0:17                   ` Brendan Higgins
2019-02-14 17:26                     ` Luis Chamberlain
2019-02-14 22:07                       ` Brendan Higgins
2018-11-28 19:36 ` [RFC v3 15/19] MAINTAINERS: add entry for KUnit the unit testing framework Brendan Higgins
2018-11-28 19:36 ` [RFC v3 16/19] arch: um: make UML unflatten device tree when testing Brendan Higgins
2018-11-28 21:16   ` Rob Herring
2018-12-04  0:00     ` Brendan Higgins
2018-11-30  3:46   ` Luis Chamberlain
2018-12-04  0:02     ` Brendan Higgins
2018-11-28 19:36 ` [RFC v3 17/19] of: unittest: migrate tests to run on KUnit Brendan Higgins
2018-11-28 20:56   ` Rob Herring
2018-11-30  0:39     ` Randy Dunlap
2018-12-04  0:13       ` Brendan Higgins
2018-12-04 13:40         ` Rob Herring
2018-12-05 23:42           ` Brendan Higgins
2018-12-07  0:41             ` Rob Herring
2018-12-04  0:08     ` Brendan Higgins
2019-02-13  1:44     ` Brendan Higgins
2019-02-14 20:10       ` Rob Herring
2019-02-14 21:52         ` Brendan Higgins
2019-02-18 22:56       ` Frank Rowand
2019-02-28  0:29         ` Brendan Higgins
2018-12-04 10:56   ` Frank Rowand
2018-11-28 19:36 ` [RFC v3 18/19] of: unittest: split out a couple of test cases from unittest Brendan Higgins
2018-12-04 10:58   ` Frank Rowand
2018-12-05 23:54     ` Brendan Higgins
2019-02-14 23:57       ` Frank Rowand
2019-02-15  0:56         ` Brendan Higgins
2019-02-15  2:05           ` Frank Rowand
2019-02-15 10:56             ` Brendan Higgins
2019-02-18 22:25               ` Frank Rowand
2019-02-20 20:44                 ` Frank Rowand
2019-02-20 20:47                   ` Frank Rowand
2019-02-28  3:52                   ` Brendan Higgins
2019-03-22  0:22                     ` Frank Rowand
2019-03-22  1:30                       ` Brendan Higgins
2019-03-22  1:47                         ` Frank Rowand
2019-03-25 22:15                           ` Brendan Higgins
2019-09-20 16:57                         ` Rob Herring
2019-09-21 23:57                           ` Frank Rowand
2019-03-22  1:34                       ` Frank Rowand
2019-03-25 22:18                         ` Brendan Higgins
2018-11-28 19:36 ` [RFC v3 19/19] of: unittest: split up some super large test cases Brendan Higgins
2018-12-04 10:52 ` [RFC v3 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework Frank Rowand
2018-12-04 11:40 ` Frank Rowand
2018-12-04 13:49   ` Rob Herring
2018-12-05 23:10     ` Brendan Higgins
2019-03-22  0:27       ` Frank Rowand
2019-03-25 22:04         ` 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=5bd5581f-f192-4ed0-6f5f-9e1bf9f443e2@cambridgegreys.com \
    --to=anton.ivanov@cambridgegreys.com \
    --cc=Alexander.Levin@microsoft.com \
    --cc=Tim.Bird@sony.com \
    --cc=arnd@arndb.de \
    --cc=brakmo@fb.com \
    --cc=brendanhiggins@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdike@addtoit.com \
    --cc=joe@perches.com \
    --cc=joel@jms.id.au \
    --cc=julia.lawall@lip6.fr \
    --cc=keescook@google.com \
    --cc=khilman@baylibre.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=knut.omang@oracle.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-um@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    /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).