On Fri, 2022-10-14 at 10:27 -0500, Justin Forbes wrote: > > Just to reiterate this is not being dropped. I did a bit of research, > CONFIG_DEBUG_WW_MUTEX_SLOWPATH was actually turned back on in 2018, as > upstream changed PROVE_LOCKING to select it. As such, there is no way > to turn it off without turning off PROVE_LOCKING. All things > considered, PROVE_LOCKING has found a good number of bugs over the > years. From the numbers you have given, there doesn't seem to be a > whole lot of opportunity for real improvement without turning off that > chain. Overall, this requires some thought on the rawhide debug > strategy more than anything else. We do have things (CKI and > similar) which can give us more useful data without making a debug > kernel default, but it still doesn't catch issues seen in hardware > drivers so much. Though if debug kernels have gotten slow enough that > no one is running them anymore, opting for the no-debug repo, we may > be better served by changing our strategy here.
My personal experience when running Rawhide on my main laptops is that, yeah, debug kernels are sufficiently slow that I will stick to booting one of the periodic non-debug builds unless I'm specifically running into a kernel bug and want to see if the debug kernel provides more information on it. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
