1. 27 2月, 2013 1 次提交
    • P
      qemu-log: default to stderr for logging output · 989b697d
      Peter Maydell 提交于
      Switch the default for qemu_log logging output from "/tmp/qemu.log"
      to stderr. This is an incompatible change in some sense, but logging
      is mostly used for debugging purposes so it shouldn't affect production
      use. The previous behaviour can be obtained by adding "-D /tmp/qemu.log"
      to the command line.
      
      This change requires us to:
       * update all the documentation/help text (we take the opportunity
         to smooth out minor inconsistencies between the phrasing in
         linux-user/bsd-user/system help messages)
       * make linux-user and bsd-user defer to qemu-log for the default
         logging destination rather than overriding it themselves
       * ensure that all logfile closing is done via qemu_log_close()
         and that that function doesn't close stderr
      as well as the obvious change to the behaviour of do_qemu_set_log()
      when no logfile name has been specified.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Message-id: 1361901160-28729-1-git-send-email-peter.maydell@linaro.org
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      989b697d
  2. 07 2月, 2013 3 次提交
    • M
      hmp: Disable chardev-add and chardev-remove · 8a14952c
      Markus Armbruster 提交于
      As a general rule, HMP commands must be built on top of the QMP API.
      Luiz and others have worked long & hard to make HMP conform to this
      rule.
      
      Commit f1088908 added chardev-add, in violation of this rule.  QMP
      command chardev-add was added right before, with minimal features, and
      the idea to complete it step by step, then switch over the HMP command
      to use it.
      
      Unfortunately, we're not there, yet, and we don't want to release with
      chardev-add in a "HMP is more powerful than QMP" state.
      
      Disable the HMP command for now, along with its chardev-remove buddy.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8a14952c
    • M
    • M
      qemu-char: Saner naming of memchar stuff & doc fixes · 3949e594
      Markus Armbruster 提交于
      New device, has never been released, so we can still improve things
      without worrying about compatibility.
      
      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.  Therefore:
      
      * Rename CirMemCharDriver to RingBufCharDriver, and call the thing a
        "ringbuf" in the API.
      
      * Rename QMP and HMP commands from memchar-FOO to ringbuf-FOO.
      
      * Rename device parameter from maxcapacity to size (simple words are
        good for you).
      
      * Clearly mark the parameter as optional in documentation.
      
      * Fix error reporting so that chardev-add reports to current monitor,
        not stderr.
      
      * Replace cirmem in C identifiers by ringbuf.
      
      * Rework documentation.  Document the impact of our crappy UTF-8
        handling on reading.
      
      * QMP examples that even work.
      
      I could split this up into multiple commits, but they'd change the
      same documentation lines multiple times.  Not worth it.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3949e594
  3. 25 1月, 2013 2 次提交
  4. 17 1月, 2013 1 次提交
  5. 16 1月, 2013 1 次提交
  6. 16 11月, 2012 1 次提交
  7. 12 11月, 2012 1 次提交
  8. 24 10月, 2012 2 次提交
  9. 29 9月, 2012 1 次提交
  10. 27 9月, 2012 1 次提交
  11. 06 9月, 2012 4 次提交
  12. 08 8月, 2012 3 次提交
  13. 07 8月, 2012 1 次提交
  14. 14 7月, 2012 1 次提交
  15. 05 6月, 2012 3 次提交
  16. 27 4月, 2012 2 次提交
  17. 20 4月, 2012 1 次提交
  18. 10 4月, 2012 1 次提交
  19. 15 3月, 2012 1 次提交
    • L
      qapi: Convert migrate · e1c37d0e
      Luiz Capitulino 提交于
      The migrate command is one of those commands where HMP and QMP completely
      mix up together. This made the conversion to the QAPI (which separates the
      command into QMP and HMP parts) a bit difficult.
      
      The first important change to be noticed is that this commit completes the
      removal of the Monitor object from migration code, started by the previous
      commit.
      
      Another important and tricky change is about supporting the non-detached
      mode. That is, if the user doesn't pass '-d' the migrate command will lock
      the monitor and will only release it when migration is finished.
      
      To support this in the new HMP command (hmp_migrate()), it is necessary
      to create a timer which runs every second and checks if the migration is
      still active. If it is, the timer callback will re-schedule itself to run
      one second in the future. If the migration has already finished, the
      monitor lock is released and the user can use it normally.
      
      All these changes should be transparent to the user.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      e1c37d0e
  20. 12 3月, 2012 1 次提交
  21. 25 2月, 2012 1 次提交
  22. 18 2月, 2012 1 次提交
  23. 26 1月, 2012 3 次提交
  24. 18 1月, 2012 3 次提交