1. 02 Aug, 2016 2 commits
    • Michael S. Tsirkin's avatar
      vhost: detect 32 bit integer wrap around · ec33d031
      Michael S. Tsirkin authored
      Detect and fail early if long wrap around is triggered.
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    • Jason Wang's avatar
      vhost: new device IOTLB API · 6b1e6cc7
      Jason Wang authored
      This patch tries to implement an device IOTLB for vhost. This could be
      used with userspace(qemu) implementation of DMA remapping
      to emulate an IOMMU for the guest.
      The idea is simple, cache the translation in a software device IOTLB
      (which is implemented as an interval tree) in vhost and use vhost_net
      file descriptor for reporting IOTLB miss and IOTLB
      update/invalidation. When vhost meets an IOTLB miss, the fault
      address, size and access can be read from the file. After userspace
      finishes the translation, it writes the translated address to the
      vhost_net file to update the device IOTLB.
      When device IOTLB is enabled by setting VIRTIO_F_IOMMU_PLATFORM all vq
      addresses set by ioctl are treated as iova instead of virtual address and
      the accessing can only be done through IOTLB instead of direct userspace
      memory access. Before each round or vq processing, all vq metadata is
      prefetched in device IOTLB to make sure no translation fault happens
      during vq processing.
      In most cases, virtqueues are contiguous even in virtual address space.
      The IOTLB translation for virtqueue itself may make it a little
      slower. We might add fast path cache on top of this patch.
      Signed-off-by: default avatarJason Wang <jasowang@redhat.com>
      [mst: use virtio feature bit: VHOST_F_DEVICE_IOTLB -> VIRTIO_F_IOMMU_PLATFORM ]
      [mst: fix build warnings ]
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      [ weiyj.lk: missing unlock on error ]
      Signed-off-by: default avatarWei Yongjun <weiyj.lk@gmail.com>
  2. 01 Aug, 2016 4 commits
  3. 10 Mar, 2016 3 commits
  4. 02 Mar, 2016 3 commits
    • Greg Kurz's avatar
      vhost: rename vhost_init_used() · 80f7d030
      Greg Kurz authored
      Looking at how callers use this, maybe we should just rename init_used
      to vhost_vq_init_access. The _used suffix was a hint that we
      access the vq used ring. But maybe what callers care about is
      that it must be called after access_ok.
      Also, this function manipulates the vq->is_le field which isn't related
      to the vq used ring.
      This patch simply renames vhost_init_used() to vhost_vq_init_access() as
      suggested by Michael.
      No behaviour change.
      Signed-off-by: default avatarGreg Kurz <gkurz@linux.vnet.ibm.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    • Greg Kurz's avatar
      vhost: rename cross-endian helpers · c5072037
      Greg Kurz authored
      The default use case for vhost is when the host and the vring have the
      same endianness (default native endianness). But there are cases where
      they differ and vhost should byteswap when accessing the vring.
      The first case is when the host is big endian and the vring belongs to
      a virtio 1.0 device, which is always little endian.
      This is covered by the vq->is_le field. This field is initialized when
      userspace calls the VHOST_SET_FEATURES ioctl. It is reset when the device
      We already have a vhost_init_is_le() helper, but the reset operation is
      opencoded as follows:
      	vq->is_le = virtio_legacy_is_little_endian();
      It isn't clear that we are resetting vq->is_le here.
      This patch moves the code to a helper with a more explicit name.
      The other case where we may have to byteswap is when the architecture can
      switch endianness at runtime (bi-endian). If endianness differs in the host
      and in the guest, then legacy devices need to be used in cross-endian mode.
      This mode is available with CONFIG_VHOST_CROSS_ENDIAN_LEGACY=y, which
      introduces a vq->user_be field. Userspace may enable cross-endian mode
      by calling the SET_VRING_ENDIAN ioctl before the device is started. The
      cross-endian mode is disabled when the device is stopped.
      The current names of the helpers that manipulate vq->user_be are unclear.
      This patch renames those helpers to clearly show that this is cross-endian
      stuff and with explicit enable/disable semantics.
      No behaviour change.
      Signed-off-by: default avatarGreg Kurz <gkurz@linux.vnet.ibm.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    • Greg Kurz's avatar
      vhost: fix error path in vhost_init_used() · e1f33be9
      Greg Kurz authored
      We don't want side effects. If something fails, we rollback vq->is_le to
      its previous value.
      Signed-off-by: default avatarGreg Kurz <gkurz@linux.vnet.ibm.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  5. 07 Dec, 2015 2 commits
  6. 27 Jul, 2015 2 commits
  7. 13 Jul, 2015 2 commits
    • Igor Mammedov's avatar
      vhost: add max_mem_regions module parameter · c9ce42f7
      Igor Mammedov authored
      it became possible to use a bigger amount of memory
      slots, which is used by memory hotplug for
      registering hotplugged memory.
      However QEMU crashes if it's used with more than ~60
      pc-dimm devices and vhost-net enabled since host kernel
      in module vhost-net refuses to accept more than 64
      memory regions.
      Allow to tweak limit via max_mem_regions module paramemter
      with default value set to 64 slots.
      Signed-off-by: default avatarIgor Mammedov <imammedo@redhat.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    • Igor Mammedov's avatar
      vhost: extend memory regions allocation to vmalloc · 4de7255f
      Igor Mammedov authored
      with large number of memory regions we could end up with
      high order allocations and kmalloc could fail if
      host is under memory pressure.
      Considering that memory regions array is used on hot path
      try harder to allocate using kmalloc and if it fails resort
      to vmalloc.
      It's still better than just failing vhost_set_memory() and
      causing guest crash due to it when a new memory hotplugged
      to guest.
      I'll still look at QEMU side solution to reduce amount of
      memory regions it feeds to vhost to make things even better,
      but it doesn't hurt for kernel to behave smarter and don't
      crash older QEMU's which could use large amount of memory
      Signed-off-by: default avatarIgor Mammedov <imammedo@redhat.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  8. 01 Jul, 2015 1 commit
  9. 01 Jun, 2015 1 commit
    • Greg Kurz's avatar
      vhost: cross-endian support for legacy devices · 2751c988
      Greg Kurz authored
      This patch brings cross-endian support to vhost when used to implement
      legacy virtio devices. Since it is a relatively rare situation, the
      feature availability is controlled by a kernel config option (not set
      by default).
      The vq->is_le boolean field is added to cache the endianness to be
      used for ring accesses. It defaults to native endian, as expected
      by legacy virtio devices. When the ring gets active, we force little
      endian if the device is modern. When the ring is deactivated, we
      revert to the native endian default.
      If cross-endian was compiled in, a vq->user_be boolean field is added
      so that userspace may request a specific endianness. This field is
      used to override the default when activating the ring of a legacy
      device. It has no effect on modern devices.
      Signed-off-by: default avatarGreg Kurz <gkurz@linux.vnet.ibm.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      Reviewed-by: default avatarCornelia Huck <cornelia.huck@de.ibm.com>
      Reviewed-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
  10. 03 Feb, 2015 1 commit
  11. 29 Dec, 2014 1 commit
    • Michael S. Tsirkin's avatar
      vhost: relax used address alignment · 5d9a07b0
      Michael S. Tsirkin authored
      virtio 1.0 only requires used address to be 4 byte aligned,
      vhost required 8 bytes (size of vring_used_elem).
      Fix up vhost to match that.
      Additionally, while vhost correctly requires 8 byte
      alignment for log, it's unconnected to used ring:
      it's a consequence that log has u64 entries.
      Tweak code to make that clearer.
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  12. 09 Dec, 2014 2 commits
  13. 09 Jun, 2014 3 commits
  14. 06 Dec, 2013 1 commit
  15. 17 Sep, 2013 1 commit
    • Qin Chuanyu's avatar
      vhost: wake up worker outside spin_lock · ac9fde24
      Qin Chuanyu authored
      the wake_up_process func is included by spin_lock/unlock in
      but it could be done outside the spin_lock.
      I have test it with kernel 3.0.27 and guest suse11-sp2 using iperf,
      the num as below.
                        original                 modified
      thread_num  tp(Gbps)   vhost(%)  |  tp(Gbps)     vhost(%)
      1           9.59        28.82    |   9.59        27.49
      8           9.61        32.92    |   9.62        26.77
      64          9.58        46.48    |   9.55        38.99
      256         9.6         63.7     |   9.6         52.59
      Signed-off-by: default avatarChuanyu Qin <qinchuanyu@huawei.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  16. 03 Sep, 2013 1 commit
  17. 20 Aug, 2013 1 commit
  18. 07 Jul, 2013 2 commits
  19. 11 Jun, 2013 1 commit
  20. 06 May, 2013 2 commits
  21. 01 May, 2013 4 commits