Lines Matching full:vmbus

43 guests as VMBus devices via the standard VMBus "offer"
44 mechanism, so they have a VMBus identity and appear under
45 /sys/bus/vmbus/devices.  The VMBus vPCI driver in Linux at
54 presented dynamically through the VMBus offer mechanism, they
59 With this approach, the vPCI device is a VMBus device and a
60 PCI device at the same time.  In response to the VMBus offer
62 VMBus connection to the vPCI VSP on the Hyper-V host.  That
63 connection has a single VMBus channel.  The channel is used to
66 is fully configured in Linux as a PCI device, the VMBus
71 the device and the hardware, with VMBus and the VMBus channel
87 bytes 4 and 5 of the instance GUID assigned to the VMBus vPCI
97 to the Hyper-V host over the VMBus channel as part of telling
123 "Eject" message sent from the host to the guest over the VMBus
129 Hyper-V over the VMBus channel indicating that the device has
130 been removed.  At this point, Hyper-V sends a VMBus rescind
131 message to the Linux guest, which the VMBus driver in Linux
132 processes by removing the VMBus identity for the device.  Once
139 return errors, and any further messages sent in the VMBus
144 Ejection Complete before sending the VMBus rescind
185 a VMBus message to the Hyper-V host and awaiting an interrupt
190 VMBus message, and then poll for the completion message. As
246 Hyper-V VMBus driver propagates cache-coherency information
247 from the VMBus node in the ACPI DSDT to all VMBus devices,
248 including vPCI devices (since they have a dual identity as a VMBus
250 Current Hyper-V versions always indicate that the VMBus is
258 messages are passed over a VMBus channel between the Hyper-V
263 the VMBus channel is first established.  See
306 messages sent over the VMBus channel associated with the vPCI