hvm/hpet: In hpet_save, call hpet_get_comparator.
authorDon Slutz <dslutz@verizon.com>
Fri, 2 May 2014 20:18:04 +0000 (16:18 -0400)
committerTim Deegan <tim@xen.org>
Thu, 8 May 2014 11:03:53 +0000 (12:03 +0100)
commita206319856c6b59b606bb27f1ee896b5ff5a74e7
tree8aaca0ea0a2df1f3efd212fe4cd81f8c68dbdb4d
parentf06ffcd4a6ea1b83cd822a9f91a2d7fb47547f34
hvm/hpet: In hpet_save, call hpet_get_comparator.

This changes save data to consistent/expected values.  It is not
technically required because hpet_get_comparator() will adjust from
any value to the correct value. And hpet_get_comparator() is
effectivly called in hpet_load via hpet_set_timer.

However it does look strange to people that the output from
xen-hvmctx for the comparator values do not change when the master
clock does.

The software-developers-hpet-spec-1-0a.pdf says that the comparator
will allways be greater than master clock for a periodic timer.

Signed-off-by: Don Slutz <dslutz@verizon.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Tim Deegan <tim@xen.org>
xen/arch/x86/hvm/hpet.c