|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH] clocksource=tsc
On 18/7/08 15:56, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:
> It appears that, for clocksource=tsc, as long as both
> read_platform_stime() and get_s_time() are returning
> scaled-tsc there can be no divergence.
>
> The issue with generating fresh time records every
> few seconds is that it unnecessarily introduces jitter
> into an otherwise ideal timesource.
I don't think this is necessarily true. If we write code to generate
accurate time records specifically for clocksource=tsc then we should easily
get accuracy down to a couple of parts per billion. This is certainly a more
pragmatic solution than extending the guest time interfaces. I am at least
coming round to the fact that the changes required in Xen's time.c are going
to have to be a bit more drastic than I first hoped.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] RE: [PATCH] clocksource=tsc, (continued)
- [Xen-devel] RE: [PATCH] clocksource=tsc, Dan Magenheimer
- [Xen-devel] Re: [PATCH] clocksource=tsc, Keir Fraser
- Re: [Xen-devel] Re: [PATCH] clocksource=tsc, Keir Fraser
- Re: [Xen-devel] Re: [PATCH] clocksource=tsc, Keir Fraser
- RE: [Xen-devel] Re: [PATCH] clocksource=tsc, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH] clocksource=tsc, Keir Fraser
- RE: [Xen-devel] Re: [PATCH] clocksource=tsc, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH] clocksource=tsc,
Keir Fraser <=
- RE: [Xen-devel] Re: [PATCH] clocksource=tsc, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH] clocksource=tsc, Keir Fraser
|
|
|
|
|