Lines Matching full:messages

56 for passing messages.   Most synthetic devices use a single channel,
64 The "in" ring buffer is for messages from the Hyper-V host to the
65 guest, and the "out" ring buffer is for messages from the guest to
105 VMBus channel messages
107 All messages sent in a VMBus channel have a standard header that includes
112 Messages follow one of two patterns:
125 Messages passed between the VSP and VSC are control messages.  For
133 ring buffer is minimal.  For example, time sync messages from the
140 Three functions exist to send VMBus channel messages:
142 1. vmbus_sendpacket():  Control-only messages and messages with
154 and valid messages, and Linux drivers for synthetic devices did not
155 fully validate messages.  With the introduction of processor
161 messages from VMBus devices.  To facilitate such validation,
162 messages read by the guest from the "in" ring buffer are copied to a
202 the guest has queued new messages in a ring buffer.  The host
220 vmbus_isr() checks for and processes any messages received on the VMBus
288 two synthetic NICs will get two offers messages with the NIC
289 class ID. The ordering of offer messages can vary from boot-to-boot
291 messages may also arrive long after Linux has initially booted
308 setup messages via the primary channel.  These messages may include
310 VSC and the VSP on the Hyper-V host.  The setup messages may also