1. 29 11月, 2012 1 次提交
  2. 03 11月, 2012 4 次提交
  3. 27 9月, 2012 1 次提交
  4. 22 7月, 2012 1 次提交
    • S
      vhost: make vhost work queue visible · 163049ae
      Stefan Hajnoczi 提交于
      The vhost work queue allows processing to be done in vhost worker thread
      context, which uses the owner process mm.  Access to the vring and guest
      memory is typically only possible from vhost worker context so it is
      useful to allow work to be queued directly by users.
      
      Currently vhost_net only uses the poll wrappers which do not expose the
      work queue functions.  However, for tcm_vhost (vhost_scsi) it will be
      necessary to queue custom work.
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Cc: Zhi Yong Wu <wuzhy@cn.ibm.com>
      Cc: Michael S. Tsirkin <mst@redhat.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NNicholas Bellinger <nab@linux-iscsi.org>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      163049ae
  5. 27 6月, 2012 1 次提交
  6. 02 5月, 2012 1 次提交
  7. 14 4月, 2012 1 次提交
  8. 20 3月, 2012 1 次提交
  9. 28 2月, 2012 2 次提交
    • M
      vhost: fix release path lockdep checks · ea5d4046
      Michael S. Tsirkin 提交于
      We shouldn't hold any locks on release path. Pass a flag to
      vhost_dev_cleanup to use the lockdep info correctly.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      Tested-by: NSasha Levin <levinsasha928@gmail.com>
      ea5d4046
    • N
      vhost: don't forget to schedule() · d550dda1
      Nadav Har'El 提交于
      This is a tiny, but important, patch to vhost.
      
      Vhost's worker thread only called schedule() when it had no work to do, and
      it wanted to go to sleep. But if there's always work to do, e.g., the guest
      is running a network-intensive program like netperf with small message sizes,
      schedule() was *never* called. This had several negative implications (on
      non-preemptive kernels):
      
       1. Passing time was not properly accounted to the "vhost" process (ps and
          top would wrongly show it using zero CPU time).
      
       2. Sometimes error messages about RCU timeouts would be printed, if the
          core running the vhost thread didn't schedule() for a very long time.
      
       3. Worst of all, a vhost thread would "hog" the core. If several vhost
          threads need to share the same core, typically one would get most of the
          CPU time (and its associated guest most of the performance), while the
          others hardly get any work done.
      
      The trivial solution is to add
      
      	if (need_resched())
      		schedule();
      
      After doing every piece of work. This will not do the heavy schedule() all
      the time, just when the timer interrupt decided a reschedule is warranted
      (so need_resched returns true).
      
      Thanks to Abel Gordon for this patch.
      Signed-off-by: NNadav Har'El <nyh@il.ibm.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      d550dda1
  10. 19 7月, 2011 5 次提交
  11. 30 5月, 2011 1 次提交
  12. 07 5月, 2011 1 次提交
  13. 09 3月, 2011 2 次提交
  14. 10 1月, 2011 1 次提交
  15. 09 12月, 2010 3 次提交
  16. 29 11月, 2010 1 次提交
  17. 04 11月, 2010 4 次提交
  18. 27 10月, 2010 1 次提交
  19. 12 10月, 2010 1 次提交
  20. 05 10月, 2010 1 次提交
    • J
      vhost: max s/g to match qemu · e0e9b406
      Jason Wang 提交于
      Qemu supports up to UIO_MAXIOV s/g so we have to match that because guest
      drivers may rely on this.
      
      Allocate indirect and log arrays dynamically to avoid using too much contigious
      memory and make the length of hdr array to match the header length since each
      iovec entry has a least one byte.
      
      Test with copying large files w/ and w/o migration in both linux and windows
      guests.
      Signed-off-by: NJason Wang <jasowang@redhat.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      e0e9b406
  21. 22 9月, 2010 1 次提交
  22. 06 9月, 2010 2 次提交
    • M
      vhost: error handling fix · 615cc221
      Michael S. Tsirkin 提交于
      vhost should set worker to NULL on cgroups attach failure,
      so that we won't try to destroy the worker again on close.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      615cc221
    • M
      vhost: fix attach to cgroups regression · 87d6a412
      Michael S. Tsirkin 提交于
      Since 2.6.36-rc1, non-root users of vhost-net fail to attach
      if they are in any cgroups.
      
      The reason is that when qemu uses vhost, vhost wants to attach
      its thread to all cgroups that qemu has.  But we got the API backwards,
      so a non-priveledged process (Qemu) tried to control
      the priveledged one (vhost), which fails.
      
      Fix this by switching to the new cgroup_attach_task_all,
      and running it from the vhost thread.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      87d6a412
  23. 02 9月, 2010 1 次提交
  24. 22 8月, 2010 1 次提交
  25. 28 7月, 2010 1 次提交