Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

2024-11-26 Thread Petr Mladek
On Thu 2024-11-21 15:56:34, John Ogness wrote: > From: Thomas Weißschuh > > The KUnit test validates the correct operation of the ringbuffer. > A separate dedicated ringbuffer is used so that the global printk > ringbuffer is not touched. Thanks a lot for upstreaming this test! > --- a/init/Kco

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

2024-11-22 Thread kernel test robot
rnel.org/r/20241121145034.123367-1-john.ogness%40linutronix.de patch subject: [PATCH printk v1] printk: ringbuffer: Add KUnit test config: i386-randconfig-141-20241122 (https://download.01.org/0day-ci/archive/20241123/202411230506.l5kqdigm-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

2024-11-22 Thread John Ogness
Hi David, On 2024-11-22, David Gow wrote: > It's a little unusual for a KUnit test -- particularly since it is > time-based and uses lots of threads. This isn't a problem, but it's > definitely a good thing that it's marked as slow. Additionally, KUnit > doesn't track any extra threads spawned, s

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

2024-11-21 Thread David Gow
On Thu, 21 Nov 2024 at 22:50, John Ogness wrote: > > From: Thomas Weißschuh > > The KUnit test validates the correct operation of the ringbuffer. > A separate dedicated ringbuffer is used so that the global printk > ringbuffer is not touched. > > Co-developed-by: John Ogness > Signed-off-by: Joh

[PATCH printk v1] printk: ringbuffer: Add KUnit test

2024-11-21 Thread John Ogness
From: Thomas Weißschuh The KUnit test validates the correct operation of the ringbuffer. A separate dedicated ringbuffer is used so that the global printk ringbuffer is not touched. Co-developed-by: John Ogness Signed-off-by: John Ogness Signed-off-by: Thomas Weißschuh --- For those not famil