On Wed, 05 Jul 2017 08:32:28 -0700
James Bottomley [off-list ref] wrote:
quoted
openSuSE has it enabled? I hope not for its production config, as
lockdep has a huge performance penalty.
Then, surely, it's the last thing we want when tracking down race
conditgions since it will alter timings dramatically.
It's to be run when you want to make sure locking order is at least not
an issue. And it's not about running when tracking down race
conditions, its to be run when developing new code.
quoted
I'm thinking you don't have it enabled. What config are you looking
at? The actual config that does the testing of locks is
CONFIG_PROVE_LOCKING, which selects LOCKDEP to be compiled in.
This is what it has:
jejb@jarvis:~/git/linux-build> grep LOCKDEP /boot/config-4.4.73-18.17-default
CONFIG_LOCKDEP_SUPPORT=y
That means your architecture supports it, it's not enabled.
-- Steve