Page MenuHomeFreeBSD

vmbus: Reorganize vmbus device tree
ClosedPublic

Authored by sepherosa_gmail.com on May 2 2017, 6:27 AM.
Tags
None
Referenced Files
F132278062: D10565.diff
Wed, Oct 15, 11:05 AM
F132217069: D10565.id27909.diff
Tue, Oct 14, 9:23 PM
Unknown Object (File)
Sun, Oct 12, 3:00 AM
Unknown Object (File)
Wed, Oct 8, 2:19 AM
Unknown Object (File)
Thu, Oct 2, 5:14 PM
Unknown Object (File)
Thu, Oct 2, 8:54 AM
Unknown Object (File)
Thu, Oct 2, 3:51 AM
Unknown Object (File)
Thu, Oct 2, 1:22 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.