[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201106104203.GC2784089@kroah.com>
Date: Fri, 6 Nov 2020 11:42:03 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Arpitha Raghunandan <98.arpi@...il.com>,
Petr Mladek <pmladek@...e.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
brendanhiggins@...gle.com, skhan@...uxfoundation.org,
rostedt@...dmis.org, sergey.senozhatsky@...il.com,
alexandre.belloni@...tlin.com, rdunlap@...radead.org,
idryomov@...il.com, kunit-dev@...glegroups.com,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v3] lib: Convert test_printf.c to KUnit
On Fri, Nov 06, 2020 at 11:31:43AM +0100, Rasmus Villemoes wrote:
> On 06/11/2020 05.04, Arpitha Raghunandan wrote:
> >
> > The total number of "atoms" can be printed by maintaining a static variable
> > total_count that can be incremented as is in the original test_printf test.
> > But, the reporting of the random seed currently is done in kselftest and so
> > will not show up with KUnit. I am not really sure which is better in this case.
>
> So my real questions are: Why do we have both kselftest and kunit?
One is testing code within the kernel image testing it within
kernelspace, and one is outside the kernel testing it from userspace.
thanks,
greg k-h
Powered by blists - more mailing lists