summaryrefslogtreecommitdiff
path: root/kernel/locking
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2021-03-01 11:13:34 +0100
committerIngo Molnar <mingo@kernel.org>2021-03-06 12:49:48 +0100
commit8d0968cc6b8ffd8496c2ebffdfdc801f949a85e5 (patch)
tree6a6051ad28d3e33ba7fca07056bfc494823be9dd /kernel/locking
parent50bf8080a94d171e843fc013abec19d8ab9f50ae (diff)
locking/csd_lock: Add boot parameter for controlling CSD lock debugging
Currently CSD lock debugging can be switched on and off via a kernel config option only. Unfortunately there is at least one problem with CSD lock handling pending for about 2 years now, which has been seen in different environments (mostly when running virtualized under KVM or Xen, at least once on bare metal). Multiple attempts to catch this issue have finally led to introduction of CSD lock debug code, but this code is not in use in most distros as it has some impact on performance. In order to be able to ship kernels with CONFIG_CSD_LOCK_WAIT_DEBUG enabled even for production use, add a boot parameter for switching the debug functionality on. This will reduce any performance impact of the debug coding to a bare minimum when not being used. Signed-off-by: Juergen Gross <jgross@suse.com> [ Minor edits. ] Signed-off-by: Ingo Molnar <mingo@kernel.org> Link: https://lore.kernel.org/r/20210301101336.7797-2-jgross@suse.com
Diffstat (limited to 'kernel/locking')
0 files changed, 0 insertions, 0 deletions