On Wed, Nov 11, 2015 at 04:33:05PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Nov 11, 2015 at 3:26 PM, Victor Kaplansky wrote:
> >
> > - Sets the logging base address.
> > + Sets logging shared memory space.
> > + When slave has VHOST_USER_PROTOCOL_F_LOG_SHMFD protocol
> > +
Hi
On Wed, Nov 11, 2015 at 3:26 PM, Victor Kaplansky wrote:
>
> - Sets the logging base address.
> + Sets logging shared memory space.
> + When slave has VHOST_USER_PROTOCOL_F_LOG_SHMFD protocol
> + feature, the log memory fd is provided in the ancillary data of
> + VHOST
On Wed, Nov 11, 2015 at 04:23:33PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Nov 11, 2015 at 4:17 PM, Michael S. Tsirkin wrote:
> > Remote doesn't know the size though, and offset is only there
> > in the current implementation.
>
> It can compute the size based on the mem tables. But it
Hi
On Wed, Nov 11, 2015 at 4:17 PM, Michael S. Tsirkin wrote:
> Remote doesn't know the size though, and offset is only there
> in the current implementation.
It can compute the size based on the mem tables. But it could be more
future-proof to add these informations.
--
Marc-André Lureau
On Wed, Nov 11, 2015 at 09:32:17AM -0500, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
> > Unlike the kernel, vhost-user application accesses log table by
> > mmaping it to its user space. This change adds two new fields to
> > VhostUserMsg payload: mmap_size, and mmap_offset and
Hi
- Original Message -
> Unlike the kernel, vhost-user application accesses log table by
> mmaping it to its user space. This change adds two new fields to
> VhostUserMsg payload: mmap_size, and mmap_offset and make QEMU to
> pass the to vhost-user application in VHOST_USER_SET_LOG_BASE
>
Unlike the kernel, vhost-user application accesses log table by
mmaping it to its user space. This change adds two new fields to
VhostUserMsg payload: mmap_size, and mmap_offset and make QEMU to
pass the to vhost-user application in VHOST_USER_SET_LOG_BASE
request.
Signed-off-by: Victor Kaplansky
