On Fri, Mar 01, 2024 at 03:14:49PM +0800, David Gow wrote:
> On Fri, 1 Mar 2024 at 01:04, Mickaël Salaün wrote:
> >
> > Run all the KUnit tests just before the first userspace code is
> > launched. This makes it it possible to write new tests that check the
> > kernel in its final state i.e., wi
: d206a76d7d2726f3b096037f2079ce0bd3ba329b
patch link:
https://lore.kernel.org/r/20240229170409.365386-2-mic%40digikod.net
patch subject: [PATCH v1 1/8] kunit: Run tests when the kernel is fully setup
config: s390-defconfig
(https://download.01.org/0day-ci/archive/20240301/202403011856.cje6do38-...@intel.com
On Fri, 1 Mar 2024 at 01:04, Mickaël Salaün wrote:
>
> Run all the KUnit tests just before the first userspace code is
> launched. This makes it it possible to write new tests that check the
> kernel in its final state i.e., with all async __init code called,
> memory and RCU properly set up, an
: d206a76d7d2726f3b096037f2079ce0bd3ba329b
patch link:
https://lore.kernel.org/r/20240229170409.365386-2-mic%40digikod.net
patch subject: [PATCH v1 1/8] kunit: Run tests when the kernel is fully setup
config: arc-allmodconfig
(https://download.01.org/0day-ci/archive/20240301/202403011330.telj6bqq-...@intel.com
Run all the KUnit tests just before the first userspace code is
launched. This makes it it possible to write new tests that check the
kernel in its final state i.e., with all async __init code called,
memory and RCU properly set up, and sysctl boot arguments evaluated.
The initial motivation is t
