1. 04 2月, 2012 7 次提交
  2. 02 2月, 2012 3 次提交
    • G
      hw/vmmouse.c: Disable vmmouse after reboot · 069ab0eb
      Gerhard Wiesinger 提交于
      Bugfix after reboot when vmmouse was enabled and another OS which uses e.g. PS/2
      mouse.
      
      Details:
      When a guest activated the vmmouse followed by a reboot the vmmouse was still
      enabled and the PS/2 mouse was therefore unsusable. When another guest is then
      booted without vmmouse support (e.g. PS/2 mouse) the mouse is not working.
      
      Reason is that VMMouse has priority and disables all other mouse entities
      and therefore must be disabled on reset.
      
      Testscenario:
      1.) Boot e.g. OS with VMMouse support (e.g. Windows with VMMouse tools)
      2.) reboot
      3.) Boot e.g. OS without VMMouse support (e.g. DOS) => PS/2 mouse doesn't work
           any more. Fixes that issue.
      
      Testscenario 2 by Jan Kiszka <jan.kiszka@siemens.com>:
      Confirm that this patch fixes a real issue. Setup: qemu.git,
      opensuse 11.4 guest, SDL graphic, system_reset while guest is using the
      vmmouse. Without the patch, the vmmouse become unusable after the
      reboot. Also, the mouse stays in absolute mode even before X starts again.
      
      Fixed by:
      Disabling the vmmouse in its reset handler.
      Tested-by: NAndreas F=E4rber <afaerber@suse.de>
      Signed-off-by: NGerhard Wiesinger <lists@wiesinger.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      069ab0eb
    • J
      mc146818rtc: Use lost_tick_policy property · 433acf0d
      Jan Kiszka 提交于
      Allow to configure the MC146818 RTC via the new lost tick policy
      property and replace rtc_td_hack with this mechanism.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      433acf0d
    • J
      qdev: Introduce lost tick policy property · 4e4fa398
      Jan Kiszka 提交于
      Potentially tick-generating timer devices will gain a common property:
      lock_tick_policy. It allows to encode 4 different ways how to deal with
      tick events the guest did not process in time:
      
      discard - ignore lost ticks (e.g. if the guest compensates for them
                already)
      delay   - replay all lost ticks in a row once the guest accepts them
                again
      merge   - if multiple ticks are lost, all of them are merged into one
                which is replayed once the guest accepts it again
      slew    - lost ticks are gradually replayed at a higher frequency than
                the original tick
      
      Not all timer device will need to support all modes. However, all need
      to accept the configuration via this common property.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      4e4fa398
  3. 31 1月, 2012 2 次提交
  4. 28 1月, 2012 28 次提交