search for: privflag

...entity. It is used for datagram + * entities created only on the host. + */ +struct datagram_entry { + struct vmci_resource resource; + u32 flags; + bool runDelayed; + vmci_datagram_recv_cb recvCB; + void *clientData; + wait_queue_head_t destroyEvent; + u32 privFlags; +}; + +struct delayed_datagram_info { + bool inDGHostQueue; + struct datagram_entry *entry; + struct vmci_datagram msg; +}; + +static atomic_t delayedDGHostQueueSize; + +static void dg_free_cb(void *clientData) +{ + struct datagram_entry *entry = (struct datagram_entry *)c...

...entity. It is used for datagram + * entities created only on the host. + */ +struct datagram_entry { + struct vmci_resource resource; + u32 flags; + bool runDelayed; + vmci_datagram_recv_cb recvCB; + void *clientData; + wait_queue_head_t destroyEvent; + u32 privFlags; +}; + +struct delayed_datagram_info { + bool inDGHostQueue; + struct datagram_entry *entry; + struct vmci_datagram msg; +}; + +static atomic_t delayedDGHostQueueSize; + +static void dg_free_cb(void *clientData) +{ + struct datagram_entry *entry = (struct datagram_entry *)c...

...vmci_hash_calc((_idx), VMCI_DOORBELL_INDEX_TABLE_SIZE) + +/* + * DoorbellEntry describes the a doorbell notification handle allocated by the + * host. + */ +struct dbell_entry { + struct vmci_resource resource; + uint32_t idx; + struct list_head idxListItem; + uint32_t privFlags; + bool runDelayed; + vmci_callback notifyCB; + void *clientData; + wait_queue_head_t destroyEvent; + atomic_t active; /* Only used by guest personality */ +}; + +/* The VMCI index table keeps track of currently registered doorbells. */ +static struct dbell_ind...

...vmci_hash_calc((_idx), VMCI_DOORBELL_INDEX_TABLE_SIZE) + +/* + * DoorbellEntry describes the a doorbell notification handle allocated by the + * host. + */ +struct dbell_entry { + struct vmci_resource resource; + uint32_t idx; + struct list_head idxListItem; + uint32_t privFlags; + bool runDelayed; + vmci_callback notifyCB; + void *clientData; + wait_queue_head_t destroyEvent; + atomic_t active; /* Only used by guest personality */ +}; + +/* The VMCI index table keeps track of currently registered doorbells. */ +static struct dbell_ind...

...+ INIT_LIST_HEAD(&ctx_list.head); + + spin_lock_init(&ctx_list.lock); + spin_lock_init(&ctx_list.firingLock); + + return VMCI_SUCCESS; +} + +/* + * Allocates and initializes a VMCI context. + */ +int vmci_ctx_init_ctx(uint32_t cid, + uint32_t privFlags, + uintptr_t eventHnd, + int userVersion, + const struct cred *cred, + struct vmci_ctx **outContext) +{ + struct vmci_ctx *context; + int result; + + if (privFlags & ~VMCI_PRIVILEGE_ALL_FLAGS) { +...

...+ INIT_LIST_HEAD(&ctx_list.head); + + spin_lock_init(&ctx_list.lock); + spin_lock_init(&ctx_list.firingLock); + + return VMCI_SUCCESS; +} + +/* + * Allocates and initializes a VMCI context. + */ +int vmci_ctx_init_ctx(uint32_t cid, + uint32_t privFlags, + uintptr_t eventHnd, + int userVersion, + const struct cred *cred, + struct vmci_ctx **outContext) +{ + struct vmci_ctx *context; + int result; + + if (privFlags & ~VMCI_PRIVILEGE_ALL_FLAGS) { +...

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

...This structure is opaque to the clients. + */ +struct vmci_qp { + struct vmci_handle handle; + struct vmci_queue *produceQ; + struct vmci_queue *consumeQ; + uint64_t produceQSize; + uint64_t consumeQSize; + uint32_t peer; + uint32_t flags; + uint32_t privFlags; + bool guestEndpoint; + uint32_t blocked; + wait_queue_head_t event; +}; + +enum qp_broker_state { + VMCIQPB_NEW, + VMCIQPB_CREATED_NO_MEM, + VMCIQPB_CREATED_MEM, + VMCIQPB_ATTACHED_NO_MEM, + VMCIQPB_ATTACHED_MEM, + VMCIQPB_SHUTDOWN_NO_MEM, +...

...This structure is opaque to the clients. + */ +struct vmci_qp { + struct vmci_handle handle; + struct vmci_queue *produceQ; + struct vmci_queue *consumeQ; + uint64_t produceQSize; + uint64_t consumeQSize; + uint32_t peer; + uint32_t flags; + uint32_t privFlags; + bool guestEndpoint; + uint32_t blocked; + wait_queue_head_t event; +}; + +enum qp_broker_state { + VMCIQPB_NEW, + VMCIQPB_CREATED_NO_MEM, + VMCIQPB_CREATED_MEM, + VMCIQPB_ATTACHED_NO_MEM, + VMCIQPB_ATTACHED_MEM, + VMCIQPB_SHUTDOWN_NO_MEM, +...

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

...scribe(u32 subid); +u32 vmci_context_get_priv_flags(u32 context_id); +int vmci_qpair_alloc(struct vmci_qp **qpair, + struct vmci_handle *handle, + uint64_t produce_qsize, + uint64_t consume_qsize, + u32 peer, u32 flags, u32 privFlags); +int vmci_qpair_detach(struct vmci_qp **qpair); +int vmci_qpair_get_produce_indexes(const struct vmci_qp *qpair, + uint64_t *producer_tail, + uint64_t *consumer_head); +int vmci_qpair_get_consume_indexes(const struct vmci_qp *qpai...

...scribe(u32 subid); +u32 vmci_context_get_priv_flags(u32 context_id); +int vmci_qpair_alloc(struct vmci_qp **qpair, + struct vmci_handle *handle, + uint64_t produce_qsize, + uint64_t consume_qsize, + u32 peer, u32 flags, u32 privFlags); +int vmci_qpair_detach(struct vmci_qp **qpair); +int vmci_qpair_get_produce_indexes(const struct vmci_qp *qpair, + uint64_t *producer_tail, + uint64_t *consumer_head); +int vmci_qpair_get_consume_indexes(const struct vmci_qp *qpai...