search for: vhost_vfio_need_reply

Displaying 20 results from an estimated 30 matches for "vhost_vfio_need_reply".

2019 Jul 04
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...e message format looks like this: > > > > > > > > > > > > struct vhost_vfio_op { > > > > > > __u64 request; > > > > > > __u32 flags; > > > > > > /* Flag values: */ > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > __u32 size; > > > > > > union { > > > > > > __u64 u64; > > > > > > struct vhost_vring_state state; > > > > > > struct vhost_vring_addr addr; > > > >...
2019 Jul 04
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...e message format looks like this: > > > > > > > > > > > > struct vhost_vfio_op { > > > > > > __u64 request; > > > > > > __u32 flags; > > > > > > /* Flag values: */ > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > __u32 size; > > > > > > union { > > > > > > __u64 u64; > > > > > > struct vhost_vring_state state; > > > > > > struct vhost_vring_addr addr; > > > >...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...is encoded in the message header too. > > > > The message format looks like this: > > > > > > > > struct vhost_vfio_op { > > > > __u64 request; > > > > __u32 flags; > > > > /* Flag values: */ > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > __u32 size; > > > > union { > > > > __u64 u64; > > > > struct vhost_vring_state state; > > > > struct vhost_vring_addr addr; > > > > } payload; > > > > }; > > >...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...is encoded in the message header too. > > > > The message format looks like this: > > > > > > > > struct vhost_vfio_op { > > > > __u64 request; > > > > __u32 flags; > > > > /* Flag values: */ > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > __u32 size; > > > > union { > > > > __u64 u64; > > > > struct vhost_vring_state state; > > > > struct vhost_vring_addr addr; > > > > } payload; > > > > }; > > >...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...ed by the `request` field in message > > header. The message size is encoded in the message header too. > > The message format looks like this: > > > > struct vhost_vfio_op { > > __u64 request; > > __u32 flags; > > /* Flag values: */ > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > __u32 size; > > union { > > __u64 u64; > > struct vhost_vring_state state; > > struct vhost_vring_addr addr; > > } payload; > > }; > > > > The existing vhost-kernel ioctl cmds are reused as the message...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...ed by the `request` field in message > > header. The message size is encoded in the message header too. > > The message format looks like this: > > > > struct vhost_vfio_op { > > __u64 request; > > __u32 flags; > > /* Flag values: */ > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > __u32 size; > > union { > > __u64 u64; > > struct vhost_vring_state state; > > struct vhost_vring_addr addr; > > } payload; > > }; > > > > The existing vhost-kernel ioctl cmds are reused as the message...
2019 Jul 04
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...t; > > > > > > > > > > struct vhost_vfio_op { > > > > > > > > __u64 request; > > > > > > > > __u32 flags; > > > > > > > > /* Flag values: */ > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > __u32 size; > > > > > > > > union { > > > > > > > > __u64 u64; > > > > > > > > struct vhost_vring_state state; > > > > > > > >...
2019 Jul 04
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...t; > > > > > > > > > > struct vhost_vfio_op { > > > > > > > > __u64 request; > > > > > > > > __u32 flags; > > > > > > > > /* Flag values: */ > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > __u32 size; > > > > > > > > union { > > > > > > > > __u64 u64; > > > > > > > > struct vhost_vring_state state; > > > > > > > >...
2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...ssages will be written to or read from this region. The message type is determined by the `request` field in message header. The message size is encoded in the message header too. The message format looks like this: struct vhost_vfio_op { __u64 request; __u32 flags; /* Flag values: */ #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ __u32 size; union { __u64 u64; struct vhost_vring_state state; struct vhost_vring_addr addr; } payload; }; The existing vhost-kernel ioctl cmds are reused as the message requests in above structure. Each message will be written to or read from this region at...
2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...ssages will be written to or read from this region. The message type is determined by the `request` field in message header. The message size is encoded in the message header too. The message format looks like this: struct vhost_vfio_op { __u64 request; __u32 flags; /* Flag values: */ #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ __u32 size; union { __u64 u64; struct vhost_vring_state state; struct vhost_vring_addr addr; } payload; }; The existing vhost-kernel ioctl cmds are reused as the message requests in above structure. Each message will be written to or read from this region at...
2018 Apr 02
2
[RFC] vhost: introduce mdev based hardware vhost backend
...essages will be written to or read from this region. The message type is determined by the `request` field in message header. The message size is encoded in the message header too. The message format looks like this: struct vhost_vfio_op { __u64 request; __u32 flags; /* Flag values: */ #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ __u32 size; union { __u64 u64; struct vhost_vring_state state; struct vhost_vring_addr addr; struct vhost_memory memory; } payload; }; The existing vhost-kernel ioctl cmds are reused as the message requests in above structure. Each message will be written t...
2018 Apr 02
2
[RFC] vhost: introduce mdev based hardware vhost backend
...essages will be written to or read from this region. The message type is determined by the `request` field in message header. The message size is encoded in the message header too. The message format looks like this: struct vhost_vfio_op { __u64 request; __u32 flags; /* Flag values: */ #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ __u32 size; union { __u64 u64; struct vhost_vring_state state; struct vhost_vring_addr addr; struct vhost_memory memory; } payload; }; The existing vhost-kernel ioctl cmds are reused as the message requests in above structure. Each message will be written t...
2019 Jul 08
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...gt; > > > > > > > > > > struct vhost_vfio_op { > > > > > > > > __u64 request; > > > > > > > > __u32 flags; > > > > > > > > /* Flag values: */ > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > __u32 size; > > > > > > > > union { > > > > > > > > __u64 u64; > > > > > > > > struct vhost_vring_state state; > > > > > > > >...
2019 Jul 08
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...gt; > > > > > > > > > > struct vhost_vfio_op { > > > > > > > > __u64 request; > > > > > > > > __u32 flags; > > > > > > > > /* Flag values: */ > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > __u32 size; > > > > > > > > union { > > > > > > > > __u64 u64; > > > > > > > > struct vhost_vring_state state; > > > > > > > >...
2019 Jul 04
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...oded in the message header too. >>>>> The message format looks like this: >>>>> >>>>> struct vhost_vfio_op { >>>>> __u64 request; >>>>> __u32 flags; >>>>> /* Flag values: */ >>>>> #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ >>>>> __u32 size; >>>>> union { >>>>> __u64 u64; >>>>> struct vhost_vring_state state; >>>>> struct vhost_vring_addr addr; >>>>> } payload; >>>>> }; >&gt...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...n. > > The message type is determined by the `request` field in message > header. The message size is encoded in the message header too. > The message format looks like this: > > struct vhost_vfio_op { > __u64 request; > __u32 flags; > /* Flag values: */ > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > __u32 size; > union { > __u64 u64; > struct vhost_vring_state state; > struct vhost_vring_addr addr; > } payload; > }; > > The existing vhost-kernel ioctl cmds are reused as the message > requests in above structure. Still a co...
2019 Jul 04
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...gt; The message format looks like this: >>>>>>> >>>>>>> struct vhost_vfio_op { >>>>>>> __u64 request; >>>>>>> __u32 flags; >>>>>>> /* Flag values: */ >>>>>>> #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ >>>>>>> __u32 size; >>>>>>> union { >>>>>>> __u64 u64; >>>>>>> struct vhost_vring_state state; >>>>>>> struct vhost_vring_addr addr; >>>>>>...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...d in message >>> header. The message size is encoded in the message header too. >>> The message format looks like this: >>> >>> struct vhost_vfio_op { >>> __u64 request; >>> __u32 flags; >>> /* Flag values: */ >>> #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ >>> __u32 size; >>> union { >>> __u64 u64; >>> struct vhost_vring_state state; >>> struct vhost_vring_addr addr; >>> } payload; >>> }; >>> >>> The existing vhost-kernel ioctl cmds...
2019 Jul 09
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...gt; > > struct vhost_vfio_op { > > > > > > > > > > __u64 request; > > > > > > > > > > __u32 flags; > > > > > > > > > > /* Flag values: */ > > > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > > > __u32 size; > > > > > > > > > > union { > > > > > > > > > > __u64 u64; > > > > > > > > > > struct vhost_vring_state state; &...
2019 Jul 09
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...gt; > > struct vhost_vfio_op { > > > > > > > > > > __u64 request; > > > > > > > > > > __u32 flags; > > > > > > > > > > /* Flag values: */ > > > > > > > > > > #define VHOST_VFIO_NEED_REPLY 0x1 /* Whether need reply */ > > > > > > > > > > __u32 size; > > > > > > > > > > union { > > > > > > > > > > __u64 u64; > > > > > > > > > > struct vhost_vring_state state; &...