Lines Matching full:message

10  * struct um_timetravel_msg - UM time travel message
12  * This is the basic message type, going in both directions.
14  * This is the message passed between the host (user-mode Linux instance)
30 	 * @seq: sequence number for the message - shall be reflected in
42 /* max number of file descriptors that can be sent/received in a message */
46  * enum um_timetravel_shared_mem_fds - fds sent in ACK message for START message
51 	 *	descriptor in the control message
56 	 *	in the control message
63  * enum um_timetravel_start_ack - ack-time mask for start message
77 	 * @UM_TIMETRAVEL_ACK: response (ACK) to any previous message,
102 	 *	this message and later	send a %UM_TIMETRAVEL_RUN message when
110 	 *	ACK message, the time in the request message is ignored
131 	 *	this is a message from the calendar telling the host that it can
134 	 *	Note that if a calendar sends this message once, the host may
149 	 * @UM_TIMETRAVEL_BROADCAST: Send/Receive a broadcast message.
150 	 *	This message can be used to sync all components in the system
151 	 *	with a single message, if the calender gets the message, the
152 	 *	calender broadcast the message to all components, and if a
154 	 *	message to it's log system.
167  * the START message, before sending any message to the controller.
188 	 *	(this includes the client itself). Otherwise, a message must
197  * The main purpose of the shared memory is to avoid all time travel message
199  * memory without the need of any client to send a message UM_TIMETRAVEL_GET
236  * @name: unique id sent to the controller by client with START message.