1. 23 8月, 2013 1 次提交
    • A
      aio / timers: Use all timerlists in icount warp calculations · ac70aafc
      Alex Bligh 提交于
      Notify all timerlists derived from vm_clock in icount warp
      calculations.
      
      When calculating timer delay based on vm_clock deadline, use
      all timerlists.
      
      For compatibility, maintain an apparent bug where when using
      icount, if no vm_clock timer was set, qemu_clock_deadline
      would return INT32_MAX and always set an icount clock expiry
      about 2 seconds ahead.
      
      NB: thread safety - when different timerlists sit on different
      threads, this will need some locking.
      Signed-off-by: NAlex Bligh <alex@alex.org.uk>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      ac70aafc
  2. 19 7月, 2013 1 次提交
  3. 22 4月, 2013 1 次提交
  4. 16 4月, 2013 1 次提交
  5. 26 3月, 2013 1 次提交
  6. 18 2月, 2013 1 次提交
  7. 12 2月, 2013 1 次提交
  8. 02 2月, 2013 1 次提交
  9. 19 12月, 2012 3 次提交
  10. 24 4月, 2012 1 次提交
  11. 03 4月, 2012 1 次提交
  12. 02 4月, 2012 1 次提交
  13. 31 3月, 2012 1 次提交
  14. 30 3月, 2012 3 次提交
    • P
      qtest: add clock management · 8156be56
      Paolo Bonzini 提交于
      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: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8156be56
    • P
      qtest: IRQ interception infrastructure · 20288345
      Paolo Bonzini 提交于
      Since /i440fx/piix3 is being removed from the composition tree, the
      IO-APIC is placed under /i440fx.  This is wrong and should be changed
      as soon as the /i440fx/piix3 path is put back.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      20288345
    • A
      qtest: add test framework · c7f0f3b1
      Anthony Liguori 提交于
      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: NAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c7f0f3b1