Page MenuHomeFreeBSD

vmbus: Reorganize vmbus device tree
ClosedPublic

Authored by sepherosa_gmail.com on May 2 2017, 6:27 AM.
Tags
None
Referenced Files
F150646234: D10565.diff
Fri, Apr 3, 1:53 AM
Unknown Object (File)
Wed, Apr 1, 10:24 PM
Unknown Object (File)
Wed, Apr 1, 7:53 AM
Unknown Object (File)
Wed, Mar 25, 1:50 AM
Unknown Object (File)
Tue, Mar 24, 10:48 PM
Unknown Object (File)
Tue, Mar 24, 9:52 PM
Unknown Object (File)
Sun, Mar 22, 8:07 PM
Unknown Object (File)
Sun, Mar 22, 5:21 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.