1. 17 1月, 2009 2 次提交
    • A
      Fix character devices after DisplayState refactoring · 2796dae0
      aliguori 提交于
      The DisplayState refactoring changed the machine init function to create a
      DisplayState for each VGA device instead of being passed an existing
      DisplayState.  This change is critical to enable multiple graphics device
      support.
      
      Unfortunately, the serial/parallel/console code is structured today to run
      before machine init to fill out the CharDriverState table which the machine
      init function uses to determine whether to create the required devices.
      
      Since a 'vc' is a type of CharDriverState, the CharDriverState code requires
      that a DisplayState exist before it runs creating a circular dependency.
      
      To fix this, this splits the creation of the initial CharDriverState from
      the initialization of the text console.  We can then in a second step associate
      a DisplayState with all TextConsoles.  This allows us to create the
      CharDriverState's first, machine init, then associate the TextConsoles with
      a DisplayState.
      
      This code screams for more cleanup.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6352 c046a42c-6fe2-441c-8c8c-71466251a162
      2796dae0
    • A
      graphical_console_init change (Stefano Stabellini) · 3023f332
      aliguori 提交于
      Patch 5/7
      
      This patch changes the graphical_console_init function to return an
      allocated DisplayState instead of a QEMUConsole.
      
      This patch contains just the graphical_console_init change and few other
      modifications mainly in console.c and vl.c.
      It was necessary to move the display frontends (e.g. sdl and vnc)
      initialization after machine->init in vl.c.
      
      This patch does *not* include any required changes to any device, these
      changes come with the following patches.
      
      Patch 6/7
      
      This patch changes the QEMUMachine init functions not to take a
      DisplayState as an argument because is not needed any more;
      
      In few places the graphic hardware initialization function was called
      only if DisplayState was not NULL, now they are always called.
      Apart from these cases, the rest are all mechanical substitutions.
      
      Patch 7/7
      
      This patch updates the graphic device code to use the new
      graphical_console_init function.
      
      As for the previous patch, in few places graphical_console_init was called
      only if DisplayState was not NULL, now it is always called.
      Apart from these cases, the rest are all mechanical substitutions.
      Signed-off-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6344 c046a42c-6fe2-441c-8c8c-71466251a162
      3023f332
  2. 16 1月, 2009 7 次提交
  3. 09 1月, 2009 2 次提交
  4. 08 1月, 2009 2 次提交
  5. 25 12月, 2008 1 次提交
  6. 23 12月, 2008 1 次提交
  7. 19 12月, 2008 1 次提交
  8. 18 12月, 2008 1 次提交
  9. 16 12月, 2008 1 次提交
  10. 11 12月, 2008 1 次提交
  11. 08 12月, 2008 1 次提交
  12. 05 12月, 2008 3 次提交
  13. 26 11月, 2008 1 次提交
    • A
      Revert r5636 to fix icount on hosts w/o high-res clocks · 357c692c
      aliguori 提交于
      Changeset r5636 changed the timers to run in the alarm callback.  The 
      alarm callback can only be called as frequently as the host alarm timer 
      fires.  For older Linux hosts and possibly non-Linux hosts, this can be 
      as high as a 1ms granularity.
      
      icount calculates the select timeout based on the next deadline and 
      select is usually capable of sleeping for a short period of time than 
      alarm timer granularity.  This means that changing the timer callbacks 
      to be based on alarm firing caused timers to fire much later than they 
      ought to when using icount.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5796 c046a42c-6fe2-441c-8c8c-71466251a162
      357c692c
  14. 19 11月, 2008 1 次提交
    • A
      gdbstub: manage CPUs as threads (Jan Kiszka) · 880a7578
      aliguori 提交于
      This patch enhances QEMU's built-in debugger for SMP guest debugging.
      Using the thread support of the gdb remote protocol, each VCPU is mapped
      on a pseudo thread and exposed to the gdb frontend. This way you can
      easy switch the focus of gdb between the VCPUs and observe their states.
      On breakpoint hit, the focus is automatically adjusted just as for
      normal multi-threaded application under gdb control.
      
      Furthermore, the patch propagates breakpoint and watchpoint insertions
      or removals to all CPUs, not just the current one as it was the case so
      far. Without this, SMP guest debugging was practically unfeasible.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5743 c046a42c-6fe2-441c-8c8c-71466251a162
      880a7578
  15. 16 11月, 2008 2 次提交
  16. 12 11月, 2008 2 次提交
  17. 11 11月, 2008 2 次提交
  18. 09 11月, 2008 1 次提交
  19. 08 11月, 2008 1 次提交
  20. 06 11月, 2008 6 次提交
  21. 01 11月, 2008 1 次提交