From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Yu, Ke" <ke.yu@intel.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Yu Ke <mr.yuke@gmail.com>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Dave Winchell <dwinchell@virtualiron.com>,
"Wei, Gang" <gang.wei@intel.com>
Subject: Re: [PATCH 0/2] range timer support
Date: Thu, 30 Oct 2008 08:35:24 +0000 [thread overview]
Message-ID: <C52F224C.1EABD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49582C73AC36CC4C8C6C42390304E81C092FCF4738@pdsmsx502.ccr.corp.intel.com>
On 30/10/08 08:31, "Yu, Ke" <ke.yu@intel.com> wrote:
> In the range-timer-use.patch, vpt timer range is [deadline, deadline+
> MIN(period/8, 1ms)], so the tick will only expire later than expected, thus
> will not trigger the issue you mentioned. Anyway, range timer is just API,
> caller has the flexibility to decide how to use it. in the HPET case, since we
> know HPET does not allow early ticks, we can dedicatedly set range to avoid
> that.
>
> If we increasing TIME_SLOP value, HPET ticks may expires sooner than expected.
Yeah, this is an argument for hacking in a new kind of slop for deadline
setting, or building on range timers (but keeping the existing timer
interface).
-- Keir
next prev parent reply other threads:[~2008-10-30 8:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 6:57 [PATCH 0/2] range timer support Yu, Ke
2008-10-28 10:54 ` Keir Fraser
2008-10-28 14:40 ` Yu Ke
2008-10-28 14:50 ` Keir Fraser
2008-10-28 11:00 ` Keir Fraser
2008-10-28 14:43 ` Yu Ke
2008-10-28 14:52 ` Keir Fraser
2008-10-28 11:38 ` Keir Fraser
2008-10-28 15:15 ` Yu Ke
2008-10-28 15:37 ` Keir Fraser
2008-10-29 2:29 ` Tian, Kevin
2008-10-29 8:28 ` Keir Fraser
2008-10-29 10:45 ` Yu Ke
2008-10-29 15:53 ` Dan Magenheimer
2008-10-30 8:31 ` Yu, Ke
2008-10-30 8:35 ` Keir Fraser [this message]
2008-10-30 8:08 ` Yu, Ke
2008-10-30 8:28 ` Keir Fraser
2008-10-30 12:47 ` Yu Ke
2008-10-31 2:23 ` Yu, Ke
2008-10-31 7:12 ` Keir Fraser
2008-10-31 7:50 ` Yu, Ke
2008-10-31 7:59 ` Keir Fraser
2008-10-31 8:37 ` Yu, Ke
2008-10-31 14:03 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C52F224C.1EABD%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=dwinchell@virtualiron.com \
--cc=gang.wei@intel.com \
--cc=jinsong.liu@intel.com \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=mr.yuke@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.