1. 26 Nov, 2014 1 commit
  2. 02 Nov, 2014 1 commit
  3. 31 Oct, 2014 1 commit
  4. 27 Oct, 2014 1 commit
    • Markus Armbruster's avatar
      aio / timers: De-document -clock · e218052f
      Markus Armbruster authored
      Commit 6d327171 "aio / timers: Remove alarm timers" has issues:
      
      1. It silently ignores -clock for backward compatibility.
      Incompatible change: -clock help no longer terminates the program.
      Tolerable.
      
      2. Failed to update option documentation.  In particular, -help still
      advises users to try -clock help for available timers.  Drop all
      documentation on -clock.
      
      3. The 'query-alarm-clock' example in docs/writing-commands.txt no
      longer works, and needs to be redone.  Can't do that right now, so I
      just stick in a FIXME.
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      e218052f
  5. 04 Oct, 2014 1 commit
  6. 01 Sep, 2014 1 commit
  7. 29 Aug, 2014 2 commits
  8. 28 Aug, 2014 1 commit
  9. 15 Aug, 2014 3 commits
  10. 06 Aug, 2014 2 commits
  11. 26 Jul, 2014 1 commit
  12. 27 Jun, 2014 1 commit
    • Anton Ivanov's avatar
      net: L2TPv3 transport · 3fb69aa1
      Anton Ivanov authored
      This transport allows to connect a QEMU nic to a static Ethernet
      over L2TPv3 tunnel. The transport supports all options present
      in the Linux kernel implementation. It allows QEMU to connect
      to any Linux host running kernel 3.3+, most routers and network
      devices as well as other QEMU instances.
      
      [Fixed up net_client_init1() switch statement to support -netdev
      --Stefan]
      Signed-off-by: default avatarAnton Ivanov <antivano@cisco.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      3fb69aa1
  13. 23 Jun, 2014 1 commit
  14. 19 Jun, 2014 4 commits
  15. 24 May, 2014 1 commit
  16. 21 May, 2014 1 commit
  17. 19 May, 2014 2 commits
    • Peter Lieven's avatar
      block: optimize zero writes with bdrv_write_zeroes · 465bee1d
      Peter Lieven authored
      this patch tries to optimize zero write requests
      by automatically using bdrv_write_zeroes if it is
      supported by the format.
      
      This significantly speeds up file system initialization and
      should speed zero write test used to test backend storage
      performance.
      
      I ran the following 2 tests on my internal SSD with a
      50G QCOW2 container and on an attached iSCSI storage.
      
      a) mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/vdX
      
      QCOW2         [off]     [on]     [unmap]
      -----
      runtime:       14secs    1.1secs  1.1secs
      filesize:      937M      18M      18M
      
      iSCSI         [off]     [on]     [unmap]
      ----
      runtime:       9.3s      0.9s     0.9s
      
      b) dd if=/dev/zero of=/dev/vdX bs=1M oflag=direct
      
      QCOW2         [off]     [on]     [unmap]
      -----
      runtime:       246secs   18secs   18secs
      filesize:      51G       192K     192K
      throughput:    203M/s    2.3G/s   2.3G/s
      
      iSCSI*        [off]     [on]     [unmap]
      ----
      runtime:       8mins     45secs   33secs
      throughput:    106M/s    1.2G/s   1.6G/s
      allocated:     100%      100%     0%
      
      * The storage was connected via an 1Gbit interface.
        It seems to internally handle writing zeroes
        via WRITESAME16 very fast.
      Signed-off-by: default avatarPeter Lieven <pl@kamp.de>
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      465bee1d
    • Matthew Booth's avatar
      curl: Add usage documentation · 0a86cb73
      Matthew Booth authored
      Signed-off-by: default avatarMatthew Booth <mbooth@redhat.com>
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      0a86cb73
  18. 27 Apr, 2014 1 commit
  19. 25 Apr, 2014 1 commit
  20. 18 Apr, 2014 1 commit
    • Michael Tokarev's avatar
      doc: grammify "allows to" · 9d85d557
      Michael Tokarev authored
      English language grammar does not allow usage
      of the word "allows" directly followed by an
      infinitive, declaring constructs like "something
      allows to do somestuff" un-grammatical.  Often
      it is possible to just insert "one" between "allows"
      and "to" to make the construct grammatical, but
      usually it is better to re-phrase the statement.
      
      This patch tries to fix 4 examples of "allows to"
      usage in qemu doc, but does not address comments
      in the code with similar constructs.  It also adds
      missing "the" in the same line.
      Signed-off-by: default avatarMichael Tokarev <mjt@tls.msk.ru>
      9d85d557
  21. 27 Mar, 2014 1 commit
  22. 17 Mar, 2014 1 commit
  23. 09 Mar, 2014 1 commit
  24. 01 Jan, 2014 1 commit
  25. 09 Dec, 2013 2 commits
    • Paolo Bonzini's avatar
      help: add id suboption to -iscsi · 2fe3798c
      Paolo Bonzini authored
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      2fe3798c
    • Vincenzo Maffione's avatar
      net: Adding netmap network backend · 58952137
      Vincenzo Maffione authored
      This patch adds support for a network backend based on netmap.
      netmap is a framework for high speed packet I/O. You can use it
      to build extremely fast traffic generators, monitors, software
      switches or network middleboxes. Its companion software switch
      VALE lets you interconnect virtual machines.
      netmap and VALE are implemented as a non-intrusive kernel module,
      support NICs from multiple vendors, are part of standard FreeBSD
      distributions and available in source format for Linux too.
      
      To compile QEMU with netmap support, use the following configure
      options:
          ./configure [...] --enable-netmap --extra-cflags=-I/path/to/netmap/sys
      where "/path/to/netmap" contains the netmap source code, available at
          http://info.iet.unipi.it/~luigi/netmap/
      
      The same webpage contains more information about the netmap project
      (together with papers and presentations).
      Signed-off-by: default avatarVincenzo Maffione <v.maffione@gmail.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      58952137
  26. 25 Nov, 2013 1 commit
  27. 18 Nov, 2013 1 commit
  28. 06 Sep, 2013 2 commits
  29. 29 Jul, 2013 1 commit
    • Markus Armbruster's avatar
      Revert "chardev: Make the name of memory device consistent" · 4f57378f
      Markus Armbruster authored
      This reverts commit 6a85e60c.
      
      Commit 51767e7c "qemu-char: Add new char backend CirMemCharDriver"
      introduced a memory ring buffer character device driver named
      "memory".  Commit 3949e594 "qemu-char: Saner naming of memchar stuff &
      doc fixes" changed the driver name to "ringbuf", along with a whole
      bunch of other names, with the following rationale:
      
          Naming is a mess.  The code calls the device driver
          CirMemCharDriver, the public API calls it "memory", "memchardev",
          or "memchar", and the special commands are named like
          "memchar-FOO".  "memory" is a particularly unfortunate choice,
          because there's another character device driver called
          MemoryDriver.  Moreover, the device's distinctive property is that
          it's a ring buffer, not that's in memory.
      
      This is what we released in 1.4.0.
      
      Unfortunately, the rename missed a critical instance of "memory": the
      actual driver name.  Thus, the new device could be used only by an
      entirely undocumented name.  The documented name did not work.
      Bummer.
      
      Commit 6a85e60c fixes this by changing the documentation to match the
      code.  It also changes some, but not all related occurences of
      "ringbuf" to "memory".  Left alone are identifiers in C code, HMP and
      QMP commands.  The latter are external interface, so they can't be
      changed.
      
      The result is an inconsistent mess.  Moreover, "memory" is a rotten
      name.  The device's distinctive property is that it's a ring buffer,
      not that's in memory.  User's don't care whether it's in RAM, flash,
      or carved into chocolate tablets by Oompa Loompas.
      
      Revert the commit.  Next commit will fix just the bug.
      
      Cc: qemu-stable@nongnu.org
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Message-id: 1374849874-25531-2-git-send-email-armbru@redhat.com
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      4f57378f
  30. 27 Jul, 2013 1 commit