From: Stephen Boyd <sboyd@kernel.org>
To: akpm@linux-foundation.org, alan.maguire@oracle.com,
anton.ivanov@cambridgegreys.com, arnd@arndb.de,
davidgow@google.com, jdike@addtoit.com, keescook@chromium.org,
richard@nod.at, rppt@linux.ibm.com, skhan@linuxfoundation.org,
yzaikin@google.com
Cc: gregkh@linuxfoundation.org, logang@deltatee.com,
mcgrof@kernel.org, knut.omang@oracle.com,
linux-um@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [RFC v1 6/6] kunit: Add 'kunit_shutdown' option
Date: Tue, 17 Dec 2019 00:06:53 -0800 [thread overview]
Message-ID: <20191217080653.B672B2082E@mail.kernel.org> (raw)
In-Reply-To: <20191216220555.245089-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-12-16 14:05:55)
> From: David Gow <davidgow@google.com>
>
> Add a new kernel command-line option, 'kunit_shutdown', which allows the
> user to specify that the kernel poweroff, halt, or reboot after
> completing all KUnit tests; this is very handy for running KUnit tests
> on UML or a VM so that the UML/VM process exits cleanly immediately
> after running all tests without needing a special initramfs.
>
> Signed-off-by: David Gow <davidgow@google.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---
> lib/kunit/executor.c | 18 ++++++++++++++++++
> tools/testing/kunit/kunit_kernel.py | 2 +-
> tools/testing/kunit/kunit_parser.py | 2 +-
> 3 files changed, 20 insertions(+), 2 deletions(-)
Can you document it in Documentation/admin-guide/kernel-parameters.txt ?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
akpm@linux-foundation.org, alan.maguire@oracle.com,
anton.ivanov@cambridgegreys.com, arnd@arndb.de,
davidgow@google.com, jdike@addtoit.com, keescook@chromium.org,
richard@nod.at, rppt@linux.ibm.com, skhan@linuxfoundation.org,
yzaikin@google.com
Cc: gregkh@linuxfoundation.org, logang@deltatee.com,
mcgrof@kernel.org, knut.omang@oracle.com,
linux-um@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [RFC v1 6/6] kunit: Add 'kunit_shutdown' option
Date: Tue, 17 Dec 2019 00:06:53 -0800 [thread overview]
Message-ID: <20191217080653.B672B2082E@mail.kernel.org> (raw)
In-Reply-To: <20191216220555.245089-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-12-16 14:05:55)
> From: David Gow <davidgow@google.com>
>
> Add a new kernel command-line option, 'kunit_shutdown', which allows the
> user to specify that the kernel poweroff, halt, or reboot after
> completing all KUnit tests; this is very handy for running KUnit tests
> on UML or a VM so that the UML/VM process exits cleanly immediately
> after running all tests without needing a special initramfs.
>
> Signed-off-by: David Gow <davidgow@google.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---
> lib/kunit/executor.c | 18 ++++++++++++++++++
> tools/testing/kunit/kunit_kernel.py | 2 +-
> tools/testing/kunit/kunit_parser.py | 2 +-
> 3 files changed, 20 insertions(+), 2 deletions(-)
Can you document it in Documentation/admin-guide/kernel-parameters.txt ?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
akpm@linux-foundation.org, alan.maguire@oracle.com,
anton.ivanov@cambridgegreys.com, arnd@arndb.de,
davidgow@google.com, jdike@addtoit.com, keescook@chromium.org,
richard@nod.at, rppt@linux.ibm.com, skhan@linuxfoundation.org,
yzaikin@google.com
Cc: linux-arch@vger.kernel.org, knut.omang@oracle.com,
gregkh@linuxfoundation.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
linux-kselftest@vger.kernel.org, logang@deltatee.com,
Brendan Higgins <brendanhiggins@google.com>,
kunit-dev@googlegroups.com
Subject: Re: [RFC v1 6/6] kunit: Add 'kunit_shutdown' option
Date: Tue, 17 Dec 2019 00:06:53 -0800 [thread overview]
Message-ID: <20191217080653.B672B2082E@mail.kernel.org> (raw)
In-Reply-To: <20191216220555.245089-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-12-16 14:05:55)
> From: David Gow <davidgow@google.com>
>
> Add a new kernel command-line option, 'kunit_shutdown', which allows the
> user to specify that the kernel poweroff, halt, or reboot after
> completing all KUnit tests; this is very handy for running KUnit tests
> on UML or a VM so that the UML/VM process exits cleanly immediately
> after running all tests without needing a special initramfs.
>
> Signed-off-by: David Gow <davidgow@google.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---
> lib/kunit/executor.c | 18 ++++++++++++++++++
> tools/testing/kunit/kunit_kernel.py | 2 +-
> tools/testing/kunit/kunit_parser.py | 2 +-
> 3 files changed, 20 insertions(+), 2 deletions(-)
Can you document it in Documentation/admin-guide/kernel-parameters.txt ?
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2019-12-17 8:06 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 22:05 [RFC v1 0/6] kunit: create a centralized executor to dispatch all KUnit tests Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-16 22:05 ` [RFC v1 1/6] vmlinux.lds.h: add linker section for KUnit test suites Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 8:21 ` Stephen Boyd
2019-12-17 8:21 ` Stephen Boyd
2019-12-17 8:21 ` Stephen Boyd
2019-12-16 22:05 ` [RFC v1 2/6] arch: um: " Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 8:21 ` Stephen Boyd
2019-12-17 8:21 ` Stephen Boyd
2019-12-17 8:21 ` Stephen Boyd
2019-12-16 22:05 ` [RFC v1 3/6] kunit: test: create a single centralized executor for all tests Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 8:04 ` Stephen Boyd
2019-12-17 8:04 ` Stephen Boyd
2019-12-17 8:04 ` Stephen Boyd
2020-01-23 22:54 ` Brendan Higgins
2020-01-23 22:54 ` Brendan Higgins
2020-01-23 22:54 ` Brendan Higgins
2019-12-16 22:05 ` [RFC v1 4/6] init: main: add KUnit to kernel init Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 7:58 ` Stephen Boyd
2019-12-17 7:58 ` Stephen Boyd
2019-12-17 7:58 ` Stephen Boyd
2020-01-23 22:45 ` Brendan Higgins
2020-01-23 22:45 ` Brendan Higgins
2020-01-23 22:45 ` Brendan Higgins
2019-12-16 22:05 ` [RFC v1 5/6] kunit: test: add test plan to KUnit TAP format Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 8:18 ` Stephen Boyd
2019-12-17 8:18 ` Stephen Boyd
2019-12-17 8:18 ` Stephen Boyd
2019-12-16 22:05 ` [RFC v1 6/6] kunit: Add 'kunit_shutdown' option Brendan Higgins
2019-12-16 22:05 ` Brendan Higgins
2019-12-17 8:06 ` Stephen Boyd [this message]
2019-12-17 8:06 ` Stephen Boyd
2019-12-17 8:06 ` Stephen Boyd
2020-01-23 22:56 ` Brendan Higgins
2020-01-23 22:56 ` Brendan Higgins
2020-01-23 22:56 ` Brendan Higgins
2020-01-06 22:40 ` [RFC v1 0/6] kunit: create a centralized executor to dispatch all KUnit tests Luis Chamberlain
2020-01-06 22:40 ` Luis Chamberlain
2020-01-23 22:40 ` Brendan Higgins
2020-01-23 22:40 ` Brendan Higgins
2020-01-23 22:40 ` Brendan Higgins
2020-01-27 17:40 ` Frank Rowand
2020-01-27 17:40 ` Frank Rowand
2020-01-27 17:40 ` Frank Rowand
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 18:36 ` Frank Rowand
2020-01-28 18:36 ` Frank Rowand
2020-01-28 18:36 ` Frank Rowand
2020-01-28 19:35 ` Tim.Bird
2020-01-28 19:35 ` Tim.Bird
2020-01-28 19:35 ` Tim.Bird
2020-01-28 19:53 ` Brendan Higgins
2020-01-28 19:53 ` Brendan Higgins
2020-01-28 19:53 ` Brendan Higgins
2020-01-29 4:24 ` Frank Rowand
2020-01-29 4:24 ` Frank Rowand
2020-01-29 4:24 ` Frank Rowand
2020-01-29 21:18 ` Brendan Higgins
2020-01-29 21:18 ` Brendan Higgins
2020-01-29 21:18 ` Brendan Higgins
2020-01-29 13:06 ` Alan Maguire
2020-01-29 13:06 ` Alan Maguire
2020-01-29 13:06 ` Alan Maguire
2020-01-29 21:28 ` Brendan Higgins
2020-01-29 21:28 ` Brendan Higgins
2020-01-29 21:28 ` Brendan Higgins
2020-03-02 19:45 ` Luis Chamberlain
2020-03-02 19:45 ` Luis Chamberlain
2020-03-02 19:45 ` Luis Chamberlain
2020-03-02 19:05 ` Luis Chamberlain
2020-03-02 19:05 ` Luis Chamberlain
2020-03-02 19:05 ` Luis Chamberlain
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=20191217080653.B672B2082E@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=arnd@arndb.de \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdike@addtoit.com \
--cc=keescook@chromium.org \
--cc=knut.omang@oracle.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=mcgrof@kernel.org \
--cc=richard@nod.at \
--cc=rppt@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=yzaikin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.