Page MenuHomeFreeBSD

vmbus: Reorganize vmbus device tree
ClosedPublic

Authored by sepherosa_gmail.com on May 2 2017, 6:27 AM.
Tags
None
Referenced Files
F147414672: D10565.id28189.diff
Tue, Mar 10, 7:18 PM
Unknown Object (File)
Mon, Mar 9, 3:56 PM
Unknown Object (File)
Mon, Mar 9, 1:17 AM
Unknown Object (File)
Sun, Mar 8, 3:25 PM
Unknown Object (File)
Sun, Mar 1, 1:06 PM
Unknown Object (File)
Sat, Feb 28, 9:24 AM
Unknown Object (File)
Jan 10 2026, 11:50 PM
Unknown Object (File)
Jan 5 2026, 9:23 PM
Subscribers
None

Details

Summary

For GEN1 Hyper-V, vmbus is attached to pcib0, which contains the resources for PCI passthrough and SR-IOV. There is no acpi_syscontainer0 on GEN1 Hyper-V.
For GEN2 Hyper-V, vmbus is attached to acpi_syscontainer0, which contains the resources for PCI passthrough and SR-IOV. There is no pcib0 on GEN2 Hyper-V.

The ACPI VMBUS device now only holds its _CRS, which is empty as of this commit; its existence is mainly for upward compatibility.

Device tree structure is suggested by jhb@.

Collabrated-wth: dexuan@
Tested-by: dexuan@

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

minor style fixes; remove unnecessary comment.

This revision was automatically updated to reflect the committed changes.