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)
Sat, Feb 8, 8:32 AM
Unknown Object (File)
Sun, Feb 2, 1:28 PM
Unknown Object (File)
Jan 18 2025, 1:38 AM
Unknown Object (File)
Jan 11 2025, 3:55 PM
Unknown Object (File)
Dec 21 2024, 11:47 PM
Unknown Object (File)
Dec 13 2024, 2:19 PM
Unknown Object (File)
Nov 25 2024, 8:41 AM
Unknown Object (File)
Nov 24 2024, 7:01 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.