|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH 0/2] range timer support
To: |
"Yu, Ke" <ke.yu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
Re: [Xen-devel] [PATCH 0/2] range timer support |
From: |
Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
Date: |
Tue, 28 Oct 2008 11:38:36 +0000 |
Cc: |
"Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx> |
Delivery-date: |
Tue, 28 Oct 2008 04:39:00 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<49582C73AC36CC4C8C6C42390304E81C092F97F902@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Ack4ymJ/w4XvWSpASU657XNxXeTXGgAJ1QxL |
Thread-topic: |
[Xen-devel] [PATCH 0/2] range timer support |
User-agent: |
Microsoft-Entourage/11.4.0.080122 |
On 28/10/08 06:57, "Yu, Ke" <ke.yu@xxxxxxxxx> wrote:
> - Per Keir's comment, more usage is found: use the range timer in HVM virtual
> periodic timer (xen/arch/x86/hvm/vpt.c). Since vpt has the logic to handle
> missing ticks, it is an ideal place to use range timer.
The fact is that just about any timer in Xen could be much sloppier than it
is. What about if we just make slop configurable and change the default up
to say 1ms? Then for lower power you could bump it some more at the cost of
things like scheduling getting a bit less accurate (and frankly does that
matter? :-). My fear with range timers is that it'll actually creep out to
nearly all current users of the timer interface, and they'll all need to
express some slightly suspect policy about how much inaccuracy they can cope
with. Fact is, in just about all cases, that's not an obvious thing to be
able to specify. In fact it's a tradeoff -- e.g., between power consumption
and 'accuracy' -- which is perhaps better centrally managed and why I think
some centrally tweakable knob like the existing SLOP macro may actually be a
better thing to work with.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|