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, Nov 22, 8:30 PM
Unknown Object (File)
Sat, Nov 16, 6:30 PM
Unknown Object (File)
Fri, Nov 15, 5:08 AM
Unknown Object (File)
Thu, Nov 14, 6:10 AM
Unknown Object (File)
Nov 12 2024, 2:17 PM
Unknown Object (File)
Nov 11 2024, 10:01 PM
Unknown Object (File)
Nov 11 2024, 9:55 AM
Unknown Object (File)
Nov 10 2024, 12:10 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.