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, frowand.list@gmail.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, linux-doc@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v1 6/7] kunit: Add 'kunit_shutdown' option
Date: Tue, 28 Jan 2020 22:33:06 -0800 [thread overview]
Message-ID: <20200129063307.19CB4206F0@mail.kernel.org> (raw)
In-Reply-To: <20200128072002.79250-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2020-01-27 23:20:01)
> 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>
> ---
Two nitpicks below
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> diff --git a/lib/kunit/executor.c b/lib/kunit/executor.c
> index 7fd16feff157e..d3ec1265a72fd 100644
> --- a/lib/kunit/executor.c
> +++ b/lib/kunit/executor.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
>
> #include <kunit/test.h>
> +#include <linux/reboot.h>
Should this include come before kunit/test.h? I imagine the order of
includes would be linux, kunit, local?
>
> /*
> * These symbols point to the .kunit_test_suites section and are defined in
> @@ -11,6 +12,23 @@ extern struct kunit_suite * const * const __kunit_suites_end[];
>
> #if IS_BUILTIN(CONFIG_KUNIT)
>
> +static char *kunit_shutdown;
> +core_param(kunit_shutdown, kunit_shutdown, charp, 0644);
> +
> +static void kunit_handle_shutdown(void)
> +{
> + if (!kunit_shutdown)
> + return;
> +
> + if (!strcmp(kunit_shutdown, "poweroff")) {
> + kernel_power_off();
> + } else if (!strcmp(kunit_shutdown, "halt")) {
> + kernel_halt();
> + } else if (!strcmp(kunit_shutdown, "reboot")) {
> + kernel_restart(NULL);
> + }
Kernel style would be to not have braces on single line if statements.
> +}
> +
> static void kunit_print_tap_header(void)
> {
> struct kunit_suite * const * const *suites, * const *subsuite;
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, frowand.list@gmail.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, linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 6/7] kunit: Add 'kunit_shutdown' option
Date: Tue, 28 Jan 2020 22:33:06 -0800 [thread overview]
Message-ID: <20200129063307.19CB4206F0@mail.kernel.org> (raw)
Message-ID: <20200129063306.sxdrL47y_GB1-JoekTwFIMvBQiFrGz2KZ_qNm4Sr4L0@z> (raw)
In-Reply-To: <20200128072002.79250-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2020-01-27 23:20:01)
> 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>
> ---
Two nitpicks below
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> diff --git a/lib/kunit/executor.c b/lib/kunit/executor.c
> index 7fd16feff157e..d3ec1265a72fd 100644
> --- a/lib/kunit/executor.c
> +++ b/lib/kunit/executor.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
>
> #include <kunit/test.h>
> +#include <linux/reboot.h>
Should this include come before kunit/test.h? I imagine the order of
includes would be linux, kunit, local?
>
> /*
> * These symbols point to the .kunit_test_suites section and are defined in
> @@ -11,6 +12,23 @@ extern struct kunit_suite * const * const __kunit_suites_end[];
>
> #if IS_BUILTIN(CONFIG_KUNIT)
>
> +static char *kunit_shutdown;
> +core_param(kunit_shutdown, kunit_shutdown, charp, 0644);
> +
> +static void kunit_handle_shutdown(void)
> +{
> + if (!kunit_shutdown)
> + return;
> +
> + if (!strcmp(kunit_shutdown, "poweroff")) {
> + kernel_power_off();
> + } else if (!strcmp(kunit_shutdown, "halt")) {
> + kernel_halt();
> + } else if (!strcmp(kunit_shutdown, "reboot")) {
> + kernel_restart(NULL);
> + }
Kernel style would be to not have braces on single line if statements.
> +}
> +
> static void kunit_print_tap_header(void)
> {
> struct kunit_suite * const * const *suites, * const *subsuite;
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, frowand.list@gmail.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, linux-doc@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v1 6/7] kunit: Add 'kunit_shutdown' option
Date: Tue, 28 Jan 2020 22:33:06 -0800 [thread overview]
Message-ID: <20200129063307.19CB4206F0@mail.kernel.org> (raw)
In-Reply-To: <20200128072002.79250-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2020-01-27 23:20:01)
> 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>
> ---
Two nitpicks below
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> diff --git a/lib/kunit/executor.c b/lib/kunit/executor.c
> index 7fd16feff157e..d3ec1265a72fd 100644
> --- a/lib/kunit/executor.c
> +++ b/lib/kunit/executor.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
>
> #include <kunit/test.h>
> +#include <linux/reboot.h>
Should this include come before kunit/test.h? I imagine the order of
includes would be linux, kunit, local?
>
> /*
> * These symbols point to the .kunit_test_suites section and are defined in
> @@ -11,6 +12,23 @@ extern struct kunit_suite * const * const __kunit_suites_end[];
>
> #if IS_BUILTIN(CONFIG_KUNIT)
>
> +static char *kunit_shutdown;
> +core_param(kunit_shutdown, kunit_shutdown, charp, 0644);
> +
> +static void kunit_handle_shutdown(void)
> +{
> + if (!kunit_shutdown)
> + return;
> +
> + if (!strcmp(kunit_shutdown, "poweroff")) {
> + kernel_power_off();
> + } else if (!strcmp(kunit_shutdown, "halt")) {
> + kernel_halt();
> + } else if (!strcmp(kunit_shutdown, "reboot")) {
> + kernel_restart(NULL);
> + }
Kernel style would be to not have braces on single line if statements.
> +}
> +
> static void kunit_print_tap_header(void)
> {
> struct kunit_suite * const * const *suites, * const *subsuite;
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, frowand.list@gmail.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,
linux-doc@vger.kernel.org, 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: [PATCH v1 6/7] kunit: Add 'kunit_shutdown' option
Date: Tue, 28 Jan 2020 22:33:06 -0800 [thread overview]
Message-ID: <20200129063307.19CB4206F0@mail.kernel.org> (raw)
In-Reply-To: <20200128072002.79250-7-brendanhiggins@google.com>
Quoting Brendan Higgins (2020-01-27 23:20:01)
> 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>
> ---
Two nitpicks below
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> diff --git a/lib/kunit/executor.c b/lib/kunit/executor.c
> index 7fd16feff157e..d3ec1265a72fd 100644
> --- a/lib/kunit/executor.c
> +++ b/lib/kunit/executor.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0
>
> #include <kunit/test.h>
> +#include <linux/reboot.h>
Should this include come before kunit/test.h? I imagine the order of
includes would be linux, kunit, local?
>
> /*
> * These symbols point to the .kunit_test_suites section and are defined in
> @@ -11,6 +12,23 @@ extern struct kunit_suite * const * const __kunit_suites_end[];
>
> #if IS_BUILTIN(CONFIG_KUNIT)
>
> +static char *kunit_shutdown;
> +core_param(kunit_shutdown, kunit_shutdown, charp, 0644);
> +
> +static void kunit_handle_shutdown(void)
> +{
> + if (!kunit_shutdown)
> + return;
> +
> + if (!strcmp(kunit_shutdown, "poweroff")) {
> + kernel_power_off();
> + } else if (!strcmp(kunit_shutdown, "halt")) {
> + kernel_halt();
> + } else if (!strcmp(kunit_shutdown, "reboot")) {
> + kernel_restart(NULL);
> + }
Kernel style would be to not have braces on single line if statements.
> +}
> +
> static void kunit_print_tap_header(void)
> {
> struct kunit_suite * const * const *suites, * const *subsuite;
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2020-01-29 6:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 7:19 [PATCH v1 0/7] kunit: create a centralized executor to dispatch all KUnit tests Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 7:19 ` [PATCH v1 1/7] vmlinux.lds.h: add linker section for KUnit test suites Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 7:19 ` [PATCH v1 2/7] arch: um: " Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-28 7:19 ` [PATCH v1 3/7] kunit: test: create a single centralized executor for all tests Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-28 7:19 ` [PATCH v1 4/7] init: main: add KUnit to kernel init Brendan Higgins
2020-01-28 7:19 ` Brendan Higgins
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-29 6:38 ` Stephen Boyd
2020-01-30 22:50 ` Brendan Higgins
2020-01-30 22:50 ` Brendan Higgins
2020-01-30 22:50 ` Brendan Higgins
2020-01-28 7:20 ` [PATCH v1 5/7] kunit: test: add test plan to KUnit TAP format Brendan Higgins
2020-01-28 7:20 ` Brendan Higgins
2020-01-28 7:20 ` [PATCH v1 6/7] kunit: Add 'kunit_shutdown' option Brendan Higgins
2020-01-28 7:20 ` Brendan Higgins
2020-01-29 6:33 ` Stephen Boyd [this message]
2020-01-29 6:33 ` Stephen Boyd
2020-01-29 6:33 ` Stephen Boyd
2020-01-29 6:33 ` Stephen Boyd
2020-01-30 22:56 ` Brendan Higgins
2020-01-30 22:56 ` Brendan Higgins
2020-01-28 7:20 ` [PATCH v1 7/7] Documentation: Add kunit_shutdown to kernel-parameters.txt Brendan Higgins
2020-01-28 7:20 ` Brendan Higgins
2020-01-29 6:27 ` Stephen Boyd
2020-01-29 6:27 ` Stephen Boyd
2020-01-29 6:27 ` Stephen Boyd
2020-01-29 6:27 ` Stephen Boyd
2020-01-30 23:04 ` Brendan Higgins
2020-01-30 23:04 ` Brendan Higgins
2020-01-30 23: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=20200129063307.19CB4206F0@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=frowand.list@gmail.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-doc@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.