[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] [HVM] RTC_UIE/RTC_SET fix

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Trolle Selander" <trolle.selander@xxxxxxxxx>
  • Date: Fri, 16 Nov 2007 10:07:48 -0800
  • Delivery-date: Fri, 16 Nov 2007 10:08:31 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=qDkLH1TWMzVZ9VQFFkIJIOCrZNPWDKP/8OOmg8VrhDZEjTR/dOleY0Hof5EquUuG/upAanHX16muthJxgf+DUdG1KeTB0FIKiio/Zy+vPwZvL9HJx5E7kEZF69Wna8eCuK/vDoKw5KutosjXH7LrK9DjQy3Drsn2IAwzLMV/U/E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

This patch fixes a bug in the RTC code which appears to originate in
having written the emuated device following an incorrect
specification. VMware has (or had, at least, at the time we were still
testing on both VMWare and Xen) the same issue. In the current code,
when RTC_SET is set, RTC_UIE is cleared. This does not match the
behavior of real hardware, where the case is simply that no update
ended interrupts are sent as long as RTC_SET is set, but the UE ints
will resume as soon as RTC_SET is cleared and the clock update is
done. This little patch fixes this issue. In practicality, this means
OS/2 can now set the time without having the clock stop. I don't know
if any other guests have been affected by this issue.

Attachment: xen-rtcuiefix.patch
Description: Text Data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.