1. 13 1月, 2013 6 次提交
  2. 10 1月, 2013 2 次提交
  3. 08 1月, 2013 1 次提交
  4. 06 1月, 2013 1 次提交
  5. 02 1月, 2013 1 次提交
  6. 01 1月, 2013 2 次提交
  7. 19 12月, 2012 5 次提交
  8. 12 12月, 2012 1 次提交
  9. 11 12月, 2012 3 次提交
  10. 09 12月, 2012 2 次提交
  11. 07 12月, 2012 1 次提交
  12. 06 12月, 2012 2 次提交
  13. 28 11月, 2012 1 次提交
    • A
      rtc: Only call rtc_set_cmos when Register B SET flag is disabled. · 02c6ccc6
      Alex Horn 提交于
      This bug occurs when the SET flag of Register B is enabled. When an RTC
      data register (i.e. any of the ten time/calender CMOS bytes) is set, the
      data is (as expected) correctly stored in the cmos_data array. However,
      since the SET flag is enabled, the function rtc_set_time is not invoked.
      As a result, the field base_rtc in RTCState remains uninitialized. This
      causes a problem on subsequent writes which can end up overwriting data.
      To see this, consider writing data to Register A after having written
      data to any of the RTC data registers; the following figure illustrates
      the call stack for the Register A write operation:
      
       +- cmos_io_port_write
       +-- check_update_timer
       +---- get_next_alarm
       +------ rtc_update_time
      
      In rtc_update_time, get_guest_rtc calculates the wrong time and
      overwrites the previously written RTC data register values.
      Signed-off-by: NAlex Horn <alex.horn@cs.ox.ac.uk>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      02c6ccc6
  14. 27 11月, 2012 1 次提交
  15. 26 11月, 2012 2 次提交
  16. 19 11月, 2012 1 次提交
  17. 15 11月, 2012 8 次提交