Page MenuHomeFreeBSD

vmbus: Reorganize vmbus device tree
ClosedPublic

Authored by sepherosa_gmail.com on May 2 2017, 6:27 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 25, 4:48 AM
Unknown Object (File)
Mar 26 2025, 5:32 AM
Unknown Object (File)
Mar 13 2025, 12:18 PM
Unknown Object (File)
Mar 4 2025, 2:32 PM
Unknown Object (File)
Feb 24 2025, 4:11 PM
Unknown Object (File)
Feb 8 2025, 8:32 AM
Unknown Object (File)
Feb 2 2025, 1:28 PM
Unknown Object (File)
Jan 18 2025, 1:38 AM
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.