1. 07 6月, 2016 1 次提交
  2. 26 5月, 2016 2 次提交
  3. 19 5月, 2016 5 次提交
  4. 23 3月, 2016 1 次提交
    • M
      include/qemu/osdep.h: Don't include qapi/error.h · da34e65c
      Markus Armbruster 提交于
      Commit 57cb38b3 included qapi/error.h into qemu/osdep.h to get the
      Error typedef.  Since then, we've moved to include qemu/osdep.h
      everywhere.  Its file comment explains: "To avoid getting into
      possible circular include dependencies, this file should not include
      any other QEMU headers, with the exceptions of config-host.h,
      compiler.h, os-posix.h and os-win32.h, all of which are doing a
      similar job to this file and are under similar constraints."
      qapi/error.h doesn't do a similar job, and it doesn't adhere to
      similar constraints: it includes qapi-types.h.  That's in excess of
      100KiB of crap most .c files don't actually need.
      
      Add the typedef to qemu/typedefs.h, and include that instead of
      qapi/error.h.  Include qapi/error.h in .c files that need it and don't
      get it now.  Include qapi-types.h in qom/object.h for uint16List.
      
      Update scripts/clean-includes accordingly.  Update it further to match
      reality: replace config.h by config-target.h, add sysemu/os-posix.h,
      sysemu/os-win32.h.  Update the list of includes in the qemu/osdep.h
      comment quoted above similarly.
      
      This reduces the number of objects depending on qapi/error.h from "all
      of them" to less than a third.  Unfortunately, the number depending on
      qapi-types.h shrinks only a little.  More work is needed for that one.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      [Fix compilation without the spice devel packages. - Paolo]
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      da34e65c
  5. 22 2月, 2016 8 次提交
  6. 16 2月, 2016 1 次提交
  7. 13 1月, 2016 1 次提交
    • M
      test-throttle: Simplify qemu_init_main_loop() error handling · 73eaa047
      Markus Armbruster 提交于
      The code looks like it tries to check for both qemu_init_main_loop()
      and qemu_get_aio_context() failure in one conditional.  In fact,
      qemu_get_aio_context() can fail only after qemu_init_main_loop()
      failed.
      
      Simplify accordingly: check for qemu_init_main_loop() error directly,
      without bothering to improve its error message.  Call
      qemu_get_aio_context() only when qemu_get_aio_context() succeeded.  It
      can't fail then, so no need to check.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Message-Id: <1450452927-8346-9-git-send-email-armbru@redhat.com>
      73eaa047
  8. 05 8月, 2015 1 次提交
  9. 21 7月, 2015 1 次提交
  10. 02 7月, 2015 1 次提交
  11. 12 6月, 2015 2 次提交
  12. 22 9月, 2014 1 次提交
    • C
      async: aio_context_new(): Handle event_notifier_init failure · 2f78e491
      Chrysostomos Nanakos 提交于
      On a system with a low limit of open files the initialization
      of the event notifier could fail and QEMU exits without printing any
      error information to the user.
      
      The problem can be easily reproduced by enforcing a low limit of open
      files and start QEMU with enough I/O threads to hit this limit.
      
      The same problem raises, without the creation of I/O threads, while
      QEMU initializes the main event loop by enforcing an even lower limit of
      open files.
      
      This commit adds an error message on failure:
      
       # qemu [...] -object iothread,id=iothread0 -object iothread,id=iothread1
       qemu: Failed to initialize event notifier: Too many open files in system
      Signed-off-by: NChrysostomos Nanakos <cnanakos@grnet.gr>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      2f78e491
  13. 18 7月, 2014 1 次提交
  14. 04 6月, 2014 2 次提交
  15. 26 10月, 2013 1 次提交
  16. 06 9月, 2013 1 次提交