[LITMUS^RT] litmus-dev Digest, Vol 81, Issue 11

[Ricardo Teixeira]

Hi,

Does anyone know if the difference between these parameters can influence
the overhead times?

396a397
> CONFIG_MUTEX_SPIN_ON_OWNER=y
601c602
< # CONFIG_HZ_250 is not set
---
> CONFIG_HZ_250=y
603,604c604,605
< CONFIG_HZ_1000=y
< CONFIG_HZ=1000
---
> # CONFIG_HZ_1000 is not set
> CONFIG_HZ=250
8208,8211c8209,8212
< CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y
< CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=1
< CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y
< CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1
---
> # CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
> CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
> # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
> CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
8214,8215c8215,8216
< CONFIG_BOOTPARAM_HUNG_TASK_PANIC=y
< CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=1
---
> # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
> CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
8231,8233c8232,8234
< CONFIG_DEBUG_RT_MUTEXES=y
< CONFIG_DEBUG_SPINLOCK=y
< CONFIG_DEBUG_MUTEXES=y
---
> # CONFIG_DEBUG_RT_MUTEXES is not set
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_DEBUG_MUTEXES is not set
8235c8236
< CONFIG_DEBUG_LOCK_ALLOC=y
---
> # CONFIG_DEBUG_LOCK_ALLOC is not set
8237d8237
< CONFIG_LOCKDEP=y
8239,8240c8239
< # CONFIG_DEBUG_LOCKDEP is not set
< CONFIG_DEBUG_ATOMIC_SLEEP=y
---
> # CONFIG_DEBUG_ATOMIC_SLEEP is not set
8843c8842
< CONFIG_SCHED_TASK_TRACE_SHIFT=12
---
> CONFIG_SCHED_TASK_TRACE_SHIFT=9
8846c8845
< CONFIG_SCHED_OVERHEAD_TRACE_SHIFT=26
---
> CONFIG_SCHED_OVERHEAD_TRACE_SHIFT=22
8848c8847
< CONFIG_SCHED_DEBUG_TRACE_SHIFT=22
---
> CONFIG_SCHED_DEBUG_TRACE_SHIFT=18

Best regards,

Ricardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190519/6ea23ab2/attachment.html>