Searched refs:VHOST_USER_SET_MEM_TABLE (Results 1 – 8 of 8) sorted by relevance
36 VHOST_USER_SET_MEM_TABLE = 5, enumerator
627 .header.request = VHOST_USER_SET_MEM_TABLE, in vhost_user_set_mem_table()
83 VHOST_USER_SET_MEM_TABLE = 5, enumerator
135 REQ(VHOST_USER_SET_MEM_TABLE), in vu_request_to_string()2095 case VHOST_USER_SET_MEM_TABLE: in vu_process_message()
76 vmsg->request == VHOST_USER_SET_MEM_TABLE) { in vmsg_unblock_fds()
68 VHOST_USER_SET_MEM_TABLE = 5, enumerator368 case VHOST_USER_SET_MEM_TABLE: in vhost_user_per_device_request()517 msg->hdr.request = VHOST_USER_SET_MEM_TABLE; in vhost_user_fill_set_mem_table_msg()939 if (msg_reply.hdr.request != VHOST_USER_SET_MEM_TABLE) { in vhost_user_set_mem_table_postcopy()942 VHOST_USER_SET_MEM_TABLE, msg_reply.hdr.request); in vhost_user_set_mem_table_postcopy()
75 VHOST_USER_SET_MEM_TABLE = 5, enumerator453 case VHOST_USER_SET_MEM_TABLE: in chr_read()
404 * ``VHOST_USER_SET_MEM_TABLE``665 ``VHOST_USER_SET_MEM_TABLE`` message. Each region has two base695 the ``VHOST_USER_SET_MEM_TABLE`` request. For invalidation events, the1138 ``VHOST_USER_SET_MEM_TABLE``1158 ``VHOST_USER_SET_MEM_TABLE`` as an acknowledgement; only upon1598 For further details on postcopy, see ``VHOST_USER_SET_MEM_TABLE``.