> (XEN) t1_cmp= 0, cur_tick= 1947268012, scheduled = negative
> 1947268012 (XEN) t1_cmp= 2147483648, cur_tick= 4258824668, scheduled
> = negative 2111341020 (XEN) t1_cmp= 0, cur_tick= 1993055268,
> scheduled = negative 1993055268 (XEN) t1_cmp= 2147483648, cur_tick=
> 3917908772, scheduled = negative 1770425124 (XEN) t1_cmp= 0,
> cur_tick= 1858024708, scheduled = negative 1858024708 (XEN) t1_cmp=
> 2147483648, cur_tick= 4000005532, scheduled = negative 1852521884
> (XEN) t1_cmp= 0, cur_tick= 2089118628, scheduled = negative
> 2089118628 (XEN) t1_cmp= 2147483648, cur_tick= 4012630076, scheduled
Keir:
From the above printk data and confimed the HW TSC frequency is
2.133GHZ, my reading to that is
1: Guest HPET frequency=2.133GHZ
2: The guest is setting comparator to 0 or 0x80000000
(2147483648 in BCD). = 1s period.
3: For some reason, current counter seems a little bit ahead
than 0x80000000 and 0, thus make a negative value to current counter,
i.e. "past" time in previous logic.
So I think the patch is mostly needed except some coding style
issues. But I didn't understand why it makes Vista wall clock slow 50%
either :-(
Thx,eddie
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|