On Wed, Jan 15, 2014 at 11:14:14AM +0200, Michael S. Tsirkin wrote:
> On Tue, Jan 14, 2014 at 07:14:53PM +0100, Antonios Motakis wrote:
> >
> >
> >
> > On Tue, Jan 14, 2014 at 12:21 PM, Michael S. Tsirkin
> > wrote:
> >
> > On Mon, Jan 13, 2014 at 03:25:17PM +0100, Antonios Motakis wrote:
On Tue, Jan 14, 2014 at 07:14:53PM +0100, Antonios Motakis wrote:
>
>
>
> On Tue, Jan 14, 2014 at 12:21 PM, Michael S. Tsirkin wrote:
>
> On Mon, Jan 13, 2014 at 03:25:17PM +0100, Antonios Motakis wrote:
> > Each ioctl request of vhost-kernel has a vhost-user message equivalent,
>
On Tue, Jan 14, 2014 at 12:21 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:17PM +0100, Antonios Motakis wrote:
> > Each ioctl request of vhost-kernel has a vhost-user message equivalent,
> > which is sent over the control socket.
> >
> > The general approach is to copy the data f
On Mon, Jan 13, 2014 at 03:25:17PM +0100, Antonios Motakis wrote:
> Each ioctl request of vhost-kernel has a vhost-user message equivalent,
> which is sent over the control socket.
>
> The general approach is to copy the data from the supplied argument
> pointer to a designated field in the messag
Each ioctl request of vhost-kernel has a vhost-user message equivalent,
which is sent over the control socket.
The general approach is to copy the data from the supplied argument
pointer to a designated field in the message. If a file descriptor is
to be passed it will be placed in the fds array f
