Page MenuHomeFreeBSD
Differential D46319

UPDATING: reference existing PR for DMAR issue
AbandonedPublic
Actions

Authored by emaste on Aug 19 2024, 1:06 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 23, 5:58 AM
Unknown Object (File)
Sun, Oct 20, 9:54 PM
Unknown Object (File)
Sat, Oct 19, 12:30 PM
Unknown Object (File)
Sep 30 2024, 2:22 AM
Unknown Object (File)
Sep 29 2024, 11:59 PM
Unknown Object (File)
Sep 12 2024, 1:43 PM
Unknown Object (File)
Sep 10 2024, 8:27 PM
Unknown Object (File)
Sep 9 2024, 4:12 AM
View All 9 Files
Subscribers
None

Details

Reviewers
imp
Summary

Encourage users to add additional detail to existing PR rather than
opening duplicates.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste requested review of this revision.Aug 19 2024, 1:06 PM
emaste created this revision.
imp added inline comments.Aug 19 2024, 1:27 PM
UPDATING
34

I specifically didn't want a single bug to turn into an omnibus. There's already two or three issues in the bug i did file. DMAR not working isn't sufficiently detailed and adding extra details to that bug for different problems will make them get lost. Separate bugs is better since duplicates can be better managed imho.

emaste abandoned this revision.Aug 20 2024, 8:14 PM

hw.dmar.enable defaults to 0 again as of 0875f3cd74b2f305e82bff4e640c89f891ca84f8, and this note in UPDATING can be removed.

There are three outstanding issues to resolve before re-enabling it by default:

  • panic in PR280817 (D46382 workaround, plus additional investigation)
  • bhyve passthrough (D25672)
  • suspend/resume (D22642, PR280950)

Revision Contents
Changeset List

PathSize
3 lines

Diff 142157

View Options

UPDATING

Loading...