Rework KUnit test execution in modules
Subsystems (10)
v4 cover Rework KUnit test execution in modules
This patch series makes two changes to how KUnit test suites are stored and executed:
- The .kunit_test_suites section is now used for tests in modules (in lieu of a module_init funciton), as well as for built-in tests. The module loader will now trigger test execution. This frees up the module_init function for other uses.
- Instead of storing an array of arrays of suites, have the kunit_test_suite() and kunit_test_suites() macros append to one global (or per-module) list of test suites. This removes a needless layer of indirection, and removes the need to NULL-terminate suite_sets.
The upshot of this is that it should now be possible to use the kunit_test_suite() and kunit_test_suites() macros to register test suites even from within modules which otherwise had module_init functions. This was proving to be quite a common issue, resulting in several modules calling into KUnit's private suite execution functions to run their tests (often introducing incompatibilities with the KUnit tooling).
This series also fixes the thunderbolt, nitro_enclaves, and sdhci-of-aspeed tests to use kunit_test_suite() now that it works. This is required, as otherwise the first two patches may break these tests entirely.
Huge thanks to Jeremy Kerr, who designed and implemented the module loader changes, and to Daniel Latypov for pushing the simplification of the nested arrays in .kunit_test_suites.
I've tested this series both with builtin tests on a number of architectures, and with modules on x86_64, and it seems good-to-go to me. More testing (particularly of modules) with more interesting setups never hurts, though!
Cheers,
-- David
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-1-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Reviewed/Acked-by tags.
Daniel Latypov (1):
kunit: flatten kunit_suite*** to kunit_suite** in .kunit_test_suites
David Gow (3):
thunderbolt: test: Use kunit_test_suite() macro
nitro_enclaves: test: Use kunit_test_suite() macro
mmc: sdhci-of-aspeed: test: Use kunit_test_suite() macro
Jeremy Kerr (1):
kunit: unify module and builtin suite definitions
drivers/mmc/host/Kconfig | 5 +- drivers/mmc/host/sdhci-of-aspeed-test.c | 8 +- drivers/mmc/host/sdhci-of-aspeed.c | 34 +---- drivers/thunderbolt/Kconfig | 6 +- drivers/thunderbolt/domain.c | 3 - drivers/thunderbolt/tb.h | 8 - drivers/thunderbolt/test.c | 12 +- drivers/virt/nitro_enclaves/Kconfig | 5 +- drivers/virt/nitro_enclaves/ne_misc_dev.c | 27 ---- .../virt/nitro_enclaves/ne_misc_dev_test.c | 5 +- include/kunit/test.h | 62 ++------ include/linux/module.h | 5 + kernel/module/main.c | 6 + lib/kunit/executor.c | 115 ++++---------- lib/kunit/executor_test.c | 144 +++++------------- lib/kunit/test.c | 54 ++++++- 16 files changed, 155 insertions(+), 344 deletions(-)
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
PATCH v4 1/5 kunit: unify module and builtin suite definitions
From: Jeremy Kerr <[email protected]>
Currently, KUnit runs built-in tests and tests loaded from modules differently. For built-in tests, the kunit_test_suite{,s}() macro adds a list of suites in the .kunit_test_suites linker section. However, for kernel modules, a module_init() function is used to run the test suites.
This causes problems if tests are included in a module which already defines module_init/exit_module functions, as they'll conflict with the kunit-provided ones.
This change removes the kunit-defined module inits, and instead parses the kunit tests from their own section in the module. After module init, we call __kunit_test_suites_init() on the contents of that section, which prepares and runs the suite.
This essentially unifies the module- and non-module kunit init formats.
---
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-2-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Reviewed-by tags.
No changes to this patch since v2:
https://lore.kernel.org/linux-kselftest/20220621085345.603820-2-davidgow at google.com/
Changes since v1:
https://lore.kernel.org/linux-kselftest/20220618090310.1174932-2-davidgow at google.com/
- Fix a compile error with CONFIG_KUNIT=m (Thanks Christophe Leroy,
kernel test robot)
- Add Ma?ra's Tested-by.
Changes since RFC:
https://lore.kernel.org/linux-kselftest/101d12fc9250b7a445ff50a9e7a25cd74d0e16eb.camel at codeconstruct.com.au/
- I've basically just rebased it, tweaked some wording, and it made it
still compile when CONFIG_MODULES is not set.
--- include/kunit/test.h | 49 +++++---------------------------------- include/linux/module.h | 5 ++++ kernel/module/main.c | 6 +++++ lib/kunit/test.c | 52 +++++++++++++++++++++++++++++++++++++++++- 4 files changed, 68 insertions(+), 44 deletions(-)
include/kunit/test.h +6 -43
@@ -250,42 +250,9 @@ static inline int kunit_run_all_tests(void) }#endif /* IS_BUILTIN(CONFIG_KUNIT) */ -#ifdef MODULE -/** -* kunit_test_suites_for_module() - used to register one or more -* &struct kunit_suite with KUnit. -* -* @__suites: a statically allocated list of &struct kunit_suite. -* -* Registers @__suites with the test framework. See &struct kunit_suite for -* more information. -* -* If a test suite is built-in, module_init() gets translated into -* an initcall which we don't want as the idea is that for builtins -* the executor will manage execution. So ensure we do not define -* module_{init|exit} functions for the builtin case when registering -* suites via kunit_test_suites() below. -*/ -#define kunit_test_suites_for_module (__suites) \ - static int __init kunit_test_suites_init(void) \ - { \ - return __kunit_test_suites_init(__suites); \ - } \ - module_init(kunit_test_suites_init); \ - \ - static void __exit kunit_test_suites_exit(void) \ - { \ - return __kunit_test_suites_exit(__suites); \ - } \ - module_exit(kunit_test_suites_exit) \ - MODULE_INFO(test, "Y"); -#else -#define kunit_test_suites_for_module (__suites) -#endif /* MODULE */ -#define __kunit_test_suites (unique_array, unique_suites, ...) \ + MODULE_INFO(test, "Y"); \ static struct kunit_suite *unique_array[] = { __VA_ARGS__, NULL }; \ - kunit_test_suites_for_module(unique_array); \ static struct kunit_suite **unique_suites \ __used __section(".kunit_test_suites") = unique_array
@@ -295,16 +262,12 @@ static inline int kunit_run_all_tests(void)* * @__suites: a statically allocated list of &struct kunit_suite. * -* Registers @suites with the test framework. See &struct kunit_suite for -* more information. -* -* When builtin, KUnit tests are all run via executor; this is done -* by placing the array of struct kunit_suite * in the .kunit_test_suites -* ELF section. +* Registers @suites with the test framework. +* This is done by placing the array of struct kunit_suite * in the +* .kunit_test_suites ELF section. * -* An alternative is to build the tests as a module. Because modules do not -* support multiple initcall()s, we need to initialize an array of suites for a -* module. +* When builtin, KUnit tests are all run via the executor at boot, and when +* built as a module, they run on module load. * */ #define kunit_test_suites(__suites...) \
include/linux/module.h +5 -0
@@ -505,6 +505,11 @@ struct module {int num_static_call_sites;struct static_call_site *static_call_sites;#endif +#if IS_ENABLED (CONFIG_KUNIT ) +int num_kunit_suites; +struct kunit_suite ***kunit_suites; +#endif +#ifdef CONFIG_LIVEPATCH bool klp;/* Is this a livepatch module? */
kernel/module/main.c +6 -0
@@ -2087,6 +2087,12 @@ static int find_module_sections(struct module *mod, struct load_info *info)sizeof (*mod->static_call_sites), &mod->num_static_call_sites);#endif +#ifdef CONFIG_KUNIT + mod->kunit_suites =section_objs (info,".kunit_test_suites" , +sizeof (*mod->kunit_suites), + &mod->num_kunit_suites); +#endif + mod->extable =section_objs (info,"__ex_table" ,sizeof (*mod->extable), &mod->num_exentries);
lib/kunit/test.c +51 -1
76 lines not on this page · raw message
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
PATCH v4 2/5 kunit: flatten kunit_suite*** to kunit_suite** in .kunit_test_suites
In reply to David GowFrom: Daniel Latypov <[email protected]>
We currently store kunit suites in the .kunit_test_suites ELF section as a struct kunit_suite*** (modulo some consts).
For every test file, we store a struct kunit_suite** NULL-terminated array.
This adds quite a bit of complexity to the test filtering code in the executor.
Instead, let's just make the .kunit_test_suites section contain a single giant array of struct kunit_suite pointers, which can then be directly manipulated. This array is not NULL-terminated, and so none of the test filtering code needs to NULL-terminate anything.
---
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-3-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Reviewed-by tags.
No changes to this patch since v2:
https://lore.kernel.org/linux-kselftest/20220621085345.603820-3-davidgow at google.com/
Changes since v1:
https://lore.kernel.org/linux-kselftest/20220618090310.1174932-3-davidgow at google.com/
- No longer NULL-terminate generated suite_sets
- Add Ma?ra's Tested-by tag.
Changes since RFC:
https://lore.kernel.org/linux-kselftest/20211013191320.2490913-1-dlatypov at google.com/
- Actually flatten the .kunit_test_suites ELF section,
rather than constructing the flattened version at runtime.
--- include/kunit/test.h | 13 ++-- include/linux/module.h | 2 +- lib/kunit/executor.c | 115 ++++++++---------------------- lib/kunit/executor_test.c | 144 +++++++++++--------------------------- lib/kunit/test.c | 18 ++--- 5 files changed, 82 insertions(+), 210 deletions(-)
include/kunit/test.h +6 -7
@@ -237,9 +237,9 @@ size_t kunit_suite_num_test_cases(struct kunit_suite *suite);unsigned int kunit_test_case_num (struct kunit_suite *suite,struct kunit_case *test_case); -int __kunit_test_suites_init (struct kunit_suite *const *const suites); +int __kunit_test_suites_init (struct kunit_suite *const *const suites,int num_suites); -void __kunit_test_suites_exit (struct kunit_suite **suites); +void __kunit_test_suites_exit (struct kunit_suite **suites,int num_suites);#if IS_BUILTIN (CONFIG_KUNIT )int kunit_run_all_tests (void );
@@ -250,11 +250,11 @@ static inline int kunit_run_all_tests(void) }#endif /* IS_BUILTIN(CONFIG_KUNIT) */ -#define __kunit_test_suites (unique_array, unique_suites, ...) \ +#define __kunit_test_suites (unique_array, ...) \ MODULE_INFO(test, "Y"); \ - static struct kunit_suite *unique_array[] = { __VA_ARGS__, NULL }; \ - static struct kunit_suite **unique_suites \ - __used __section(".kunit_test_suites") = unique_array + static struct kunit_suite *unique_array[] \ + __aligned(sizeof(struct kunit_suite *)) \ + __used __section(".kunit_test_suites") = { __VA_ARGS__ }/** * kunit_test_suites() - used to register one or more &struct kunit_suite
@@ -272,7 +272,6 @@ static inline int kunit_run_all_tests(void)*/ #define kunit_test_suites(__suites...) \ __kunit_test_suites(__UNIQUE_ID(array), \ - __UNIQUE_ID(suites), \ ##__suites)#define kunit_test_suite (suite) kunit_test_suites(&suite)
include/linux/module.h +1 -1
@@ -507,7 +507,7 @@ struct module {#endif #if IS_ENABLED (CONFIG_KUNIT )int num_kunit_suites; -struct kunit_suite ***kunit_suites; +struct kunit_suite **kunit_suites;#endif
lib/kunit/executor.c +28 -87
182 lines not on this page · raw message
lib/kunit/executor_test.c +41 -103
195 lines not on this page · raw message
lib/kunit/test.c +6 -12
@@ -586,11 +586,11 @@ static void kunit_init_suite(struct kunit_suite *suite) suite->suite_init_err =0 ; } -int __kunit_test_suites_init (struct kunit_suite *const *const suites) +int __kunit_test_suites_init (struct kunit_suite *const *const suites,int num_suites) {unsigned int i; -for (i =0 ; suites[i] !=NULL ; i++) { +for (i =0 ; i < num_suites; i++) {kunit_init_suite (suites[i]);kunit_run_tests (suites[i]); }
@@ -603,11 +603,11 @@ static void kunit_exit_suite(struct kunit_suite *suite)kunit_debugfs_destroy_suite (suite); } -void __kunit_test_suites_exit (struct kunit_suite **suites) +void __kunit_test_suites_exit (struct kunit_suite **suites,int num_suites) {unsigned int i; -for (i =0 ; suites[i] !=NULL ; i++) +for (i =0 ; i < num_suites; i++)kunit_exit_suite (suites[i]); kunit_suite_counter =1 ;
@@ -617,18 +617,12 @@ EXPORT_SYMBOL_GPL(__kunit_test_suites_exit);#ifdef CONFIG_MODULES static void kunit_module_init (struct module *mod) { -unsigned int i; - -for (i =0 ; i < mod->num_kunit_suites; i++) -__kunit_test_suites_init (mod->kunit_suites[i]); +__kunit_test_suites_init (mod->kunit_suites, mod->num_kunit_suites); }static void kunit_module_exit (struct module *mod) { -unsigned int i; - -for (i =0 ; i < mod->num_kunit_suites; i++) -__kunit_test_suites_exit (mod->kunit_suites[i]); +__kunit_test_suites_exit (mod->kunit_suites, mod->num_kunit_suites); } static int kunit_module_notify(struct notifier_block *nb, unsigned long val,
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
PATCH v4 3/5 thunderbolt: test: Use kunit_test_suite() macro
In reply to David GowThe new implementation of kunit_test_suite() for modules no longer conflicts with module_init, so can now be used by the thunderbolt tests.
Also update the Kconfig entry to enable the test when KUNIT_ALL_TESTS is enabled.
This means that kunit_tool can now successfully run and parse the test results with, for example:
./tools/testing/kunit/kunit.py run --arch=x86_64 \ --kconfig_add CONFIG_PCI=y --kconfig_add CONFIG_USB4=y \ 'thunderbolt'
---
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-4-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Acked-by tag.
Changes since v2:
https://lore.kernel.org/linux-kselftest/20220621085345.603820-4-davidgow at google.com/
- Don't permit USB4_KUNIT_TESTS to be enabled when USB4=y and KUNIT=m i.e., add a dependency on (USB4=m || KUNIT=y)
This would result in undefined kunit symbols being used, otherwise.
- Add Daniel's Acked-by
Changes since v1:
https://lore.kernel.org/linux-kselftest/20220618090310.1174932-4-davidgow at google.com/
- Actually include the Kconfig changes, which were mistakenly added to
the next patch in the series in v1.
- Add Acked-by tag from Mika Westerberg
--- drivers/thunderbolt/Kconfig | 6 ++++-- drivers/thunderbolt/domain.c | 3 --- drivers/thunderbolt/tb.h | 8 -------- drivers/thunderbolt/test.c | 12 +----------- 4 files changed, 5 insertions(+), 24 deletions(-)
drivers/thunderbolt/Kconfig +4 -2
@@ -28,8 +28,10 @@ config USB4_DEBUGFS_WRITE this for production systems or distro kernels. config USB4_KUNIT_TEST - bool "KUnit tests" - depends on KUNIT=y + bool "KUnit tests" if !KUNIT_ALL_TESTS + depends on (USB4=m || KUNIT=y) + depends on KUNIT + default KUNIT_ALL_TESTS config USB4_DMA_TEST tristate "DMA traffic test driver"
drivers/thunderbolt/domain.c +0 -3
@@ -872,7 +872,6 @@ int tb_domain_init(void) {int ret; -tb_test_init ();tb_debugfs_init ();tb_acpi_init ();
@@ -890,7 +889,6 @@ int tb_domain_init(void) err_acpi:tb_acpi_exit ();tb_debugfs_exit (); -tb_test_exit ();return ret; }
@@ -903,5 +901,4 @@ void tb_domain_exit(void)tb_xdomain_exit ();tb_acpi_exit ();tb_debugfs_exit (); -tb_test_exit (); }
drivers/thunderbolt/tb.h +0 -8
@@ -1271,12 +1271,4 @@ static inline void tb_service_debugfs_init(struct tb_service *svc) { }static inline void tb_service_debugfs_remove (struct tb_service *svc) { }#endif -#ifdef CONFIG_USB4_KUNIT_TEST -int tb_test_init (void ); -void tb_test_exit (void ); -#else -static inline int tb_test_init (void ) {return 0 ; } -static inline void tb_test_exit (void ) { } -#endif -#endif
drivers/thunderbolt/test.c +1 -11
@@ -2817,14 +2817,4 @@ static struct kunit_suite tb_test_suite = { .test_cases = tb_test_cases, }; -static struct kunit_suite *tb_test_suites[] = { &tb_test_suite,NULL }; - -int tb_test_init (void ) -{ -return __kunit_test_suites_init (tb_test_suites); -} - -void tb_test_exit (void ) -{ -return __kunit_test_suites_exit (tb_test_suites); -} +kunit_test_suite (tb_test_suite);
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
PATCH v4 4/5 nitro_enclaves: test: Use kunit_test_suite() macro
In reply to David GowThe kunit_test_suite() macro previously conflicted with module_init, making it unsuitable for use in the nitro_enclaves test. Now that it's fixed, we can use it instead of a custom call into internal KUnit functions to run the test.
As a side-effect, this means that the test results are properly included with other suites when built-in. To celebrate, enable the test by default when KUNIT_ALL_TESTS is set (and NITRO_ENCLAVES enabled).
The nitro_enclave tests can now be run via kunit_tool with:
./tools/testing/kunit/kunit.py run --arch=x86_64 \ --kconfig_add CONFIG_PCI=y --kconfig_add CONFIG_SMP=y \ --kconfig_add CONFIG_HOTPLUG_CPU=y \ --kconfig_add CONFIG_VIRT_DRIVERS=y \ --kconfig_add CONFIG_NITRO_ENCLAVES=y \ 'ne_misc_dev_test'
(This is a pretty long command, so it may be worth adding a .kunitconfig file at some point, instead.)
---
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-5-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Acked-by tag.
Changes since v2:
https://lore.kernel.org/linux-kselftest/20220621085345.603820-5-davidgow at google.com/
- Add Andra's Reviewed-by tag.
Changes since v1:
https://lore.kernel.org/linux-kselftest/20220618090310.1174932-5-davidgow at google.com/
- Move the mistakenly-added thunderbolt Kconfig to the previous patch (Thanks Andra)
- Add Andra's Acked-by tag.
--- drivers/virt/nitro_enclaves/Kconfig | 5 ++-- drivers/virt/nitro_enclaves/ne_misc_dev.c | 27 ------------------- .../virt/nitro_enclaves/ne_misc_dev_test.c | 5 +--- 3 files changed, 4 insertions(+), 33 deletions(-)
drivers/virt/nitro_enclaves/Kconfig +3 -2
@@ -16,8 +16,9 @@ config NITRO_ENCLAVES The module will be called nitro_enclaves. config NITRO_ENCLAVES_MISC_DEV_TEST - bool "Tests for the misc device functionality of the Nitro Enclaves" - depends on NITRO_ENCLAVES && KUNIT=y + bool "Tests for the misc device functionality of the Nitro Enclaves" if !KUNIT_ALL_TESTS + depends on NITRO_ENCLAVES && KUNIT + default KUNIT_ALL_TESTS help Enable KUnit tests for the misc device functionality of the Nitro Enclaves. Select this option only if you will boot the kernel for
drivers/virt/nitro_enclaves/ne_misc_dev.c +0 -27
@@ -1759,35 +1759,10 @@ static long ne_ioctl(struct file *file, unsigned int cmd, unsigned long arg)#if defined(CONFIG_NITRO_ENCLAVES_MISC_DEV_TEST )#include "ne_misc_dev_test.c" - -static inline int ne_misc_dev_test_init (void ) -{ -return __kunit_test_suites_init (ne_misc_dev_test_suites); -} - -static inline void ne_misc_dev_test_exit (void ) -{ -__kunit_test_suites_exit (ne_misc_dev_test_suites); -} -#else -static inline int ne_misc_dev_test_init (void ) -{ -return 0 ; -} - -static inline void ne_misc_dev_test_exit (void ) -{ -}#endif static int __init ne_init (void ) { -int rc =0 ; - - rc =ne_misc_dev_test_init (); -if (rc <0 ) -return rc; -mutex_init (&ne_cpu_pool.mutex);return pci_register_driver (&ne_pci_driver);
@@ -1798,8 +1773,6 @@ static void __exit ne_exit(void)pci_unregister_driver (&ne_pci_driver);ne_teardown_cpu_pool (); - -ne_misc_dev_test_exit (); }module_init (ne_init);
drivers/virt/nitro_enclaves/ne_misc_dev_test.c +1 -4
@@ -151,7 +151,4 @@ static struct kunit_suite ne_misc_dev_test_suite = { .test_cases = ne_misc_dev_test_cases, }; -static struct kunit_suite *ne_misc_dev_test_suites[] = { - &ne_misc_dev_test_suite, -NULL -}; +kunit_test_suite (ne_misc_dev_test_suite);
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
PATCH v4 5/5 mmc: sdhci-of-aspeed: test: Use kunit_test_suite() macro
In reply to David GowThe kunit_test_suite() macro is no-longer incompatible with module_add, so its use can be reinstated.
Since this fixes parsing with builtins and kunit_tool, also enable the test by default when KUNIT_ALL_TESTS is enabled.
The test can now be run via kunit_tool with:
./tools/testing/kunit/kunit.py run --arch=x86_64 \ --kconfig_add CONFIG_OF=y --kconfig_add CONFIG_OF_ADDRESS=y \ --kconfig_add CONFIG_MMC=y --kconfig_add CONFIG_MMC_SDHCI=y \ --kconfig_add CONFIG_MMC_SDHCI_PLTFM=y \ --kconfig_add CONFIG_MMC_SDHCI_OF_ASPEED=y \ 'sdhci-of-aspeed'
(It may be worth adding a .kunitconfig at some point, as there are enough dependencies to make that command scarily long.)
---
Changes since v3:
https://lore.kernel.org/linux-kselftest/20220625050838.1618469-6-davidgow at google.com/
- Rebase on top of the TAINT_TEST patch series. This should now apply
cleanly on top of the kunit branch:
https://lore.kernel.org/linux-kselftest/20220708044847.531566-1-davidgow at google.com/T/#u
- Add Brendan's Acked-by tag.
Changes since v2:
https://lore.kernel.org/linux-kselftest/20220621085345.603820-6-davidgow at google.com/
- Clean up the aspeed_sdc_init() function to get rid of an obsolete goto (Thanks Daniel)
- Add Daniel and Ulf's Acked-by tags.
No changes since v1:
https://lore.kernel.org/linux-kselftest/20220618090310.1174932-6-davidgow at google.com/
--- drivers/mmc/host/Kconfig | 5 ++-- drivers/mmc/host/sdhci-of-aspeed-test.c | 8 +----- drivers/mmc/host/sdhci-of-aspeed.c | 34 +------------------------ 3 files changed, 5 insertions(+), 42 deletions(-)
drivers/mmc/host/Kconfig +3 -2
@@ -169,8 +169,9 @@ config MMC_SDHCI_OF_ASPEED If unsure, say N. config MMC_SDHCI_OF_ASPEED_TEST - bool "Tests for the ASPEED SDHCI driver" - depends on MMC_SDHCI_OF_ASPEED && KUNIT=y + bool "Tests for the ASPEED SDHCI driver" if !KUNIT_ALL_TESTS + depends on MMC_SDHCI_OF_ASPEED && KUNIT + default KUNIT_ALL_TESTS help Enable KUnit tests for the ASPEED SDHCI driver. Select this option only if you will boot the kernel for the purpose of running
drivers/mmc/host/sdhci-of-aspeed-test.c +1 -7
@@ -96,10 +96,4 @@ static struct kunit_suite aspeed_sdhci_test_suite = { .test_cases = aspeed_sdhci_test_cases, }; -static struct kunit_suite *aspeed_sdc_test_suite_array[] = { - &aspeed_sdhci_test_suite, -NULL , -}; - -static struct kunit_suite **aspeed_sdc_test_suites - __used __section(".kunit_test_suites") = aspeed_sdc_test_suite_array; +kunit_test_suite (aspeed_sdhci_test_suite);
drivers/mmc/host/sdhci-of-aspeed.c +1 -33
@@ -606,25 +606,6 @@ static struct platform_driver aspeed_sdc_driver = {#if defined(CONFIG_MMC_SDHCI_OF_ASPEED_TEST )#include "sdhci-of-aspeed-test.c" - -static inline int aspeed_sdc_tests_init (void ) -{ -return __kunit_test_suites_init (aspeed_sdc_test_suites); -} - -static inline void aspeed_sdc_tests_exit (void ) -{ -__kunit_test_suites_exit (aspeed_sdc_test_suites); -} -#else -static inline int aspeed_sdc_tests_init (void ) -{ -return 0 ; -} - -static inline void aspeed_sdc_tests_exit (void ) -{ -}#endif static int __init aspeed_sdc_init (void )
@@ -637,18 +618,7 @@ static int __init aspeed_sdc_init(void) rc =platform_driver_register (&aspeed_sdc_driver);if (rc <0 ) - goto cleanup_sdhci; - - rc =aspeed_sdc_tests_init (); -if (rc <0 ) { -platform_driver_unregister (&aspeed_sdc_driver); - goto cleanup_sdhci; - } - -return 0 ; - -cleanup_sdhci: -platform_driver_unregister (&aspeed_sdhci_driver); +platform_driver_unregister (&aspeed_sdhci_driver);return rc; }
@@ -656,8 +626,6 @@ module_init(aspeed_sdc_init); static void __exit aspeed_sdc_exit(void) { -aspeed_sdc_tests_exit (); -platform_driver_unregister (&aspeed_sdc_driver);platform_driver_unregister (&aspeed_sdhci_driver); }
Signature · 1 line
2.37.0.rc0.161.g10f37bed90-goog
Re: [PATCH v4 1/5] kunit: unify module and builtin suite definitions
In reply to David GowHi David, Jeremy,
Quoted 16 lines · David Gow
From: Jeremy Kerr <[email protected]>
Currently, KUnit runs built-in tests and tests loaded from modules differently. For built-in tests, the kunit_test_suite{,s}() macro adds a list of suites in the .kunit_test_suites linker section. However, for kernel modules, a
module_init()function is used to run the test suites.This causes problems if tests are included in a module which already defines module_init/exit_module functions, as they'll conflict with the kunit-provided ones.
This change removes the kunit-defined module inits, and instead parses the kunit tests from their own section in the module. After module init, we call
__kunit_test_suites_init()on the contents of that section, which prepares and runs the suite.
Quoted 7 lines
This essentially unifies the module- and non-module kunit init formats.
Tested-by Ma?ra Canal <[email protected]>Reviewed-by Brendan Higgins <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Daniel Latypov <[email protected]>Signed-off-by David Gow <[email protected]>
Thanks for your patch, which is now commit 3d6e44623841c8b8 ("kunit:
unify module and builtin suite definitions") upstream.
Since this commit, modular kunit tests are no longer run at all.
Before:
# insmod lib/kunit/kunit.ko
# insmod lib/test_hash.ko
test_hash: loading test module taints kernel.
# Subtest: hash
1..2
ok 1 - test_string_or
ok 2 - test_hash_or
# hash: pass:2 fail:0 skip:0 total:2
# Totals: pass:2 fail:0 skip:0 total:2
ok 1 - hashAfter:
# insmod lib/kunit/kunit.ko
# insmod lib/test_hash.ko
test_hash: loading test module taints kernel.The actual test code (and test init code, if it exists) is not run.
Reverting commits e5857d396f35e59e ("kunit: flatten kunit_suite*** to kunit_suite** in .kunit_test_suites") and 3d6e44623841c8b8 ("kunit:
unify module and builtin suite definitions") fixes the issue.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: [PATCH v4 1/5] kunit: unify module and builtin suite definitions
Quoted 52 lines · Geert Uytterhoeven
Hi David, Jeremy,
Quoted 16 lines · David Gow
From: Jeremy Kerr <[email protected]>
Currently, KUnit runs built-in tests and tests loaded from modules differently. For built-in tests, the kunit_test_suite{,s}() macro adds a list of suites in the .kunit_test_suites linker section. However, for kernel modules, a
module_init()function is used to run the test suites.This causes problems if tests are included in a module which already defines module_init/exit_module functions, as they'll conflict with the kunit-provided ones.
This change removes the kunit-defined module inits, and instead parses the kunit tests from their own section in the module. After module init, we call
__kunit_test_suites_init()on the contents of that section, which prepares and runs the suite.Quoted 7 lines
This essentially unifies the module- and non-module kunit init formats.
Tested-by Ma?ra Canal <[email protected]>Reviewed-by Brendan Higgins <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Daniel Latypov <[email protected]>Signed-off-by David Gow <[email protected]>Thanks for your patch, which is now commit
3d6e44623841c8b8("kunit:
unify module and builtin suite definitions") upstream.Since this commit, modular kunit tests are no longer run at all.
Before:
# insmod lib/kunit/kunit.ko # insmod lib/test_hash.ko test_hash: loading test module taints kernel. # Subtest: hash 1..2 ok 1 - test_string_or ok 2 - test_hash_or # hash: pass:2 fail:0 skip:0 total:2 # Totals: pass:2 fail:0 skip:0 total:2 ok 1 - hashAfter:
# insmod lib/kunit/kunit.ko # insmod lib/test_hash.ko test_hash: loading test module taints kernel.
Quoted 5 lines
The actual test code (and test init code, if it exists) is not run.
Reverting commits
e5857d396f35e59e("kunit: flatten kunit_suite*** to kunit_suite** in .kunit_test_suites") and3d6e44623841c8b8("kunit:
unify module and builtin suite definitions") fixes the issue.
Thanks Geert,
This is a known issue. There's a patch to fix it here, which just
missed the pull request:
https://patchwork.kernel.org/project/linux-kselftest/patch/20220713005221.1926290-1-davidgow at google.com/
We'll try to get it merged as soon as possible.
Cheers,
-- David
Re: [PATCH v4 1/5] kunit: unify module and builtin suite definitions
Hi David,
Quoted 56 lines · David Gow
Quoted 49 lines · Geert Uytterhoeven
Quoted 16 lines · David Gow
From: Jeremy Kerr <[email protected]>
Currently, KUnit runs built-in tests and tests loaded from modules differently. For built-in tests, the kunit_test_suite{,s}() macro adds a list of suites in the .kunit_test_suites linker section. However, for kernel modules, a
module_init()function is used to run the test suites.This causes problems if tests are included in a module which already defines module_init/exit_module functions, as they'll conflict with the kunit-provided ones.
This change removes the kunit-defined module inits, and instead parses the kunit tests from their own section in the module. After module init, we call
__kunit_test_suites_init()on the contents of that section, which prepares and runs the suite.Quoted 7 lines
This essentially unifies the module- and non-module kunit init formats.
Tested-by Ma?ra Canal <[email protected]>Reviewed-by Brendan Higgins <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Daniel Latypov <[email protected]>Signed-off-by David Gow <[email protected]>Thanks for your patch, which is now commit
3d6e44623841c8b8("kunit:
unify module and builtin suite definitions") upstream.Since this commit, modular kunit tests are no longer run at all.
Before:
# insmod lib/kunit/kunit.ko # insmod lib/test_hash.ko test_hash: loading test module taints kernel. # Subtest: hash 1..2 ok 1 - test_string_or ok 2 - test_hash_or # hash: pass:2 fail:0 skip:0 total:2 # Totals: pass:2 fail:0 skip:0 total:2 ok 1 - hashAfter:
# insmod lib/kunit/kunit.ko # insmod lib/test_hash.ko test_hash: loading test module taints kernel.Quoted 5 lines
The actual test code (and test init code, if it exists) is not run.
Reverting commits
e5857d396f35e59e("kunit: flatten kunit_suite*** to kunit_suite** in .kunit_test_suites") and3d6e44623841c8b8("kunit:
unify module and builtin suite definitions") fixes the issue.
Quoted 7 lines
Thanks Geert,
This is a known issue. There's a patch to fix it here, which just
missed the pull request:
https://patchwork.kernel.org/project/linux-kselftest/patch/20220713005221.1926290-1-davidgow at google.com/We'll try to get it merged as soon as possible.
Thanks for the pointer. I can confirm it fixes the issue, so I provided my Tb tag.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds