[LTP] [RFC PATCH] starvation: set a baseline for maximum runtime

[Cyril Hrubis]

Hi!
> I have carefully compared the differences between the general
> kernel config-file and the debug kernel config-file.
> 
> Below are some configurations that are only enabled in the debug
> kernel and may cause kernel performance degradation.
> 
> The rough thoughts I have is to create a SET for those configurations,
> If the SUT kernel maps some of them, we reset the timeout using the
> value multiplier obtained from calibration.
> 
> e.g. if mapped N number of the configs we use (timeout * N) as the
> max_runtime.
> 
> Or next, we extract this method to the whole LTP timeout setting if
> possible?

That actually sounds good to me, if we detect certain kernel options
that are know to slow down the process execution it makes a good sense
to multiply the timeouts for all tests directly in the test library.

> #Lock debugging:
> CONFIG_PROVE_LOCKING
> CONFIG_LOCKDEP
> CONFIG_DEBUG_SPINLOCK
> 
> #Mutex debugging
> CONFIG_DEBUG_RT_MUTEXES=y
> CONFIG_DEBUG_MUTEXES=y
> 
> #Memory debugging:
> CONFIG_DEBUG_PAGEALLOC
> CONFIG_KASAN
> CONFIG_SLUB_RCU_DEBUG
> 
> #Tracing and profiling:
> CONFIG_TRACE_IRQFLAGS
> CONFIG_LATENCYTOP
> CONFIG_DEBUG_NET
> 
> #Filesystem debugging:
> CONFIG_EXT4_DEBUG
> CONFIG_QUOTA_DEBUG
> 
> #Miscellaneous debugging:
> CONFIG_FAULT_INJECTION
> CONFIG_DEBUG_OBJECTS

-- 
Cyril Hrubis
chrubis@suse.cz