1. 12 Apr, 2012 1 commit
  2. 30 Mar, 2012 2 commits
    • Paolo Bonzini's avatar
      qtest: add clock management · 8156be56
      Paolo Bonzini authored
      This patch combines qtest and -icount together to turn the vm_clock
      into a source that can be fully managed by the client.  To this end new
      commands clock_step and clock_set are added.  Hooking them with libqtest
      is left as an exercise to the reader.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      8156be56
    • Anthony Liguori's avatar
      qtest: add test framework · c7f0f3b1
      Anthony Liguori authored
      The idea behind qtest is pretty simple.  Instead of executing a CPU via TCG or
      KVM, rely on an external process to send events to the device model that the CPU
      would normally generate.
      
      qtest presents itself as an accelerator.  In addition, a new option is added to
      establish a qtest server (-qtest) that takes a character device.  This is what
      allows the external process to send CPU events to the device model.
      
      qtest uses a simple line based protocol to send the events.  Documentation of
      that protocol is in qtest.c.
      
      I considered reusing the monitor for this job.  Adding interrupts would be a bit
      difficult.  In addition, logging would also be difficult.
      
      qtest has extensive logging support.  All protocol commands are logged with
      time stamps using a new command line option (-qtest-log).  Logging is important
      since ultimately, this is a feature for debugging.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      c7f0f3b1
  3. 14 Mar, 2012 1 commit
    • Andreas Färber's avatar
      Rename CPUState -> CPUArchState · 9349b4f9
      Andreas Färber authored
      Scripted conversion:
        for file in *.[hc] hw/*.[hc] hw/kvm/*.[hc] linux-user/*.[hc] linux-user/m68k/*.[hc] bsd-user/*.[hc] darwin-user/*.[hc] tcg/*/*.[hc] target-*/cpu.h; do
          sed -i "s/CPUState/CPUArchState/g" $file
        done
      
      All occurrences of CPUArchState are expected to be replaced by QOM CPUState,
      once all targets are QOM'ified and common fields have been extracted.
      Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
      Reviewed-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      9349b4f9
  4. 18 Feb, 2012 4 commits
  5. 19 Jan, 2012 1 commit
  6. 12 Jan, 2012 1 commit
  7. 15 Dec, 2011 1 commit
  8. 12 Dec, 2011 1 commit
  9. 06 Dec, 2011 4 commits
  10. 05 Dec, 2011 1 commit
  11. 02 Dec, 2011 1 commit
  12. 07 Nov, 2011 1 commit
  13. 01 Nov, 2011 1 commit
  14. 27 Oct, 2011 1 commit
  15. 21 Oct, 2011 5 commits
  16. 19 Oct, 2011 1 commit
    • Luiz Capitulino's avatar
      runstate: Allow user to migrate twice · 8a9236f1
      Luiz Capitulino authored
      It should be a matter of allowing the transition POSTMIGRATE ->
      FINISH_MIGRATE, but it turns out that the VM won't do the
      transition the second time because it's already stopped.
      
      So this commit also adds vm_stop_force_state() which performs
      the transition even if the VM is already stopped.
      
      While there also allow other states to migrate.
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      8a9236f1
  17. 20 Sep, 2011 1 commit
  18. 15 Sep, 2011 3 commits
  19. 02 Sep, 2011 1 commit
    • Anthony Liguori's avatar
      main: force enabling of I/O thread · 12d4536f
      Anthony Liguori authored
      Enabling the I/O thread by default seems like an important part of declaring
      1.0.  Besides allowing true SMP support with KVM, the I/O thread means that the
      TCG VCPU doesn't have to multiplex itself with the I/O dispatch routines which
      currently requires a (racey) signal based alarm system.
      
      I know there have been concerns about performance.  I think so far the ones that
      have come up (virtio-net) are most likely due to secondary reasons like
      decreased batching.
      
      I think we ought to force enabling I/O thread early in 1.0 development and
      commit to resolving any lingering issues.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      12d4536f
  20. 22 Aug, 2011 2 commits
  21. 20 Aug, 2011 1 commit
  22. 23 Jul, 2011 1 commit
  23. 16 Jul, 2011 2 commits
  24. 26 Jun, 2011 1 commit
  25. 24 Jun, 2011 1 commit