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)
Feb 15 2024, 2:39 AM
Unknown Object (File)
Jan 7 2024, 10:54 AM
Unknown Object (File)
Dec 23 2023, 12:21 AM
Unknown Object (File)
Dec 13 2023, 12:07 AM
Unknown Object (File)
Nov 24 2023, 8:31 AM
Unknown Object (File)
Nov 14 2023, 9:07 PM
Unknown Object (File)
Nov 7 2023, 11:14 PM
Unknown Object (File)
Nov 5 2023, 10:28 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.