Page MenuHomeFreeBSD

Use MTX_SYSINIT for the VESA lock.
ClosedPublic

Authored by jhb on Jul 22 2016, 9:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 14, 11:01 PM
Unknown Object (File)
Mon, Apr 14, 6:46 AM
Unknown Object (File)
Mon, Apr 14, 3:24 AM
Unknown Object (File)
Mon, Apr 14, 1:47 AM
Unknown Object (File)
Mon, Apr 14, 1:46 AM
Unknown Object (File)
Mon, Apr 14, 1:44 AM
Unknown Object (File)
Thu, Apr 3, 1:48 PM
Unknown Object (File)
Mar 8 2025, 1:47 AM
Subscribers

Details

Summary

Use MTX_SYSINIT for the VESA lock.

vesa_init_done isn't a reliable guard for the mutex init. If
vesa_configure() doesn't find valid VESA info it will not set
vesa_init_done, but the lock will remain initialized. Revert r303076
and use MTX_SYSINIT to deterministically init the lock.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 4584
Build 4637: arc lint + arc unit

Event Timeline

jhb retitled this revision from to Use MTX_SYSINIT for the VESA lock..
jhb updated this object.
jhb edited the test plan for this revision. (Show Details)
jhb added reviewers: royger, dumbbell.
  • Don't explicitly destroy the lock.
royger edited edge metadata.

I cannot test this ATM (I might be able to do it tomorrow), but it looks fine, and AFAICT it should also solve the issue I was seeing. Thanks for taking care of this (and sorry for messing it up)!

This revision is now accepted and ready to land.Jul 23 2016, 9:43 AM

Oh, forgot to ask, but since I'm not going to MFC r303076 could you please MFC this to stable/11?

Thanks.

This revision was automatically updated to reflect the committed changes.