1. 28 5月, 2014 1 次提交
  2. 24 5月, 2014 1 次提交
  3. 10 5月, 2014 1 次提交
    • K
      vl.c: remove init_clocks call from main · 02ce232c
      Kirill Batuzov 提交于
      Clocks are initialized in qemu_init_main_loop. They are not needed before it.
      Initializing them twice is not only unnecessary but is harmful: it results in
      memory leak and potentially can lead to a situation where different parts of
      QEMU use different sets of timers.
      
      To avoid it remove init_clocks call from main and add an assertion to
      qemu_clock_init that corresponding clock has not been initialized yet.
      Signed-off-by: NKirill Batuzov <batuzovk@ispras.ru>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      02ce232c
  4. 06 5月, 2014 5 次提交
  5. 28 4月, 2014 3 次提交
  6. 27 4月, 2014 2 次提交
  7. 18 4月, 2014 1 次提交
  8. 27 3月, 2014 1 次提交
  9. 25 3月, 2014 1 次提交
    • S
      osdep: initialize glib threads in all QEMU tools · ae2990c2
      Stefan Hajnoczi 提交于
      glib versions prior to 2.31.0 require an explicit g_thread_init() call
      to enable multi-threading.
      
      Failure to initialize threading causes glib to take single-threaded code
      paths without synchronization.  For example, the g_slice allocator will
      crash due to race conditions.
      
      Fix this for all QEMU tool programs (qemu-nbd, qemu-io, qemu-img) by
      moving the g_thread_init() call from vl.c:main() into a new
      osdep.c:thread_init() constructor function.
      
      thread_init() has __attribute__((constructor)) and is automatically
      invoked by the runtime during startup.
      
      We can now drop the "simple" trace backend's g_thread_init() call since
      thread_init() already called it.
      
      Note that we must keep coroutine-gthread.c's g_thread_init() call which
      is located in a constructor function.  There is no guarantee for
      constructor function ordering so thread_init() may only be called later.
      Reported-by: NMario de Chenno <mario.dechenno@unina2.it>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      ae2990c2
  10. 20 3月, 2014 3 次提交
  11. 19 3月, 2014 1 次提交
  12. 17 3月, 2014 2 次提交
  13. 14 3月, 2014 2 次提交
  14. 13 3月, 2014 2 次提交
  15. 10 3月, 2014 2 次提交
  16. 09 3月, 2014 1 次提交
  17. 05 3月, 2014 1 次提交
  18. 03 3月, 2014 1 次提交
  19. 27 2月, 2014 1 次提交
    • M
      sun4m: Add Sun CG3 framebuffer initialisation function · af87bf29
      Mark Cave-Ayland 提交于
      In order to allow the user to choose the framebuffer for sparc-softmmu, add
      -vga tcx and -vga cg3 options to the QEMU command line. If no option is
      specified, the default TCX framebuffer is used.
      
      Since proprietary FCode ROMs use a resolution of 1152x900, slightly relax the
      validation rules to allow both displays to be initiated at the higher
      resolution used by these ROMs upon request (OpenBIOS FCode ROMs default to
      the normal QEMU sun4m default resolution of 1024x768).
      
      Finally move any fprintf(stderr ...) statements in the areas affected by this
      patch over to the new error_report() function.
      Signed-off-by: NMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
      CC: Blue Swirl <blauwirbel@gmail.com>
      CC: Anthony Liguori <aliguori@amazon.com>
      CC: Peter Maydell <peter.maydell@linaro.org>
      CC: Bob Breuer <breuerr@mc.net>
      CC: Artyom Tarasenko <atar4qemu@gmail.com>
      af87bf29
  20. 20 2月, 2014 1 次提交
  21. 18 2月, 2014 1 次提交
  22. 15 2月, 2014 4 次提交
  23. 14 2月, 2014 1 次提交
  24. 05 2月, 2014 1 次提交