From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: TIME_SLOP vs. timer_slop
Date: Wed, 10 Feb 2010 13:28:37 +0000 [thread overview]
Message-ID: <C7986505.9B69%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B72A96C020000780002EB6B@vpn.id2.novell.com>
On 10/02/2010 11:41, "Jan Beulich" <JBeulich@novell.com> wrote:
> is there a reason why schedule.c and timer.c don't both use the latter,
> command line controllable value?
>
> Also, aren't the comment and code in vcpu_periodic_timer_work() out
> of sync with the actual implementation in timer.c in that a timer will
> never expire early (with timer_slop only being used to set an upper
> bound on the expiry range)?
Yes, true. Thanks for that; it's now fixed as c/s 20921.
-- Keir
prev parent reply other threads:[~2010-02-10 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 11:41 TIME_SLOP vs. timer_slop Jan Beulich
2010-02-10 13:28 ` Keir Fraser [this message]
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=C7986505.9B69%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).