| Message ID | 20181108093111.5943-1-daniel.vetter@ffwll.ch (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | HAX FOR CI: Enable cross-release | expand |
Quoting Daniel Vetter (2018-11-08 09:31:11) > Only way to convince our CI to enable stuff that's new and defaulting > to off. Obviously not for merging. See DRM_I915_DEBUG where we define what extras we need for CI. -Chris
On Thu, Nov 08, 2018 at 09:41:47AM +0000, Chris Wilson wrote: > Quoting Daniel Vetter (2018-11-08 09:31:11) > > Only way to convince our CI to enable stuff that's new and defaulting > > to off. Obviously not for merging. > > See DRM_I915_DEBUG where we define what extras we need for CI. Yeah I know, just not sure whether I really want to push this through or not. Seems quite a bit more fragile to resurrect than it originally looked like. There's also the issue that we'd need serious buy-in from a bunch of people before we can enable this in our CI for real. -Daniel
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 6074fa3463ac..deba9af0f418 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -1095,6 +1095,7 @@ config LOCKDEP_CROSSRELEASE bool "Enable cross-release checking" depends on PROVE_LOCKING select LOCKDEP_COMPLETIONS + default y help This makes lockdep work for crosslock which is a lock allowed to be released in a different context from the acquisition context.
Only way to convince our CI to enable stuff that's new and defaulting to off. Obviously not for merging. v2: Also enable fullstack backtraces. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> --- lib/Kconfig.debug | 1 + 1 file changed, 1 insertion(+)