All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Yu, Ke" <ke.yu@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Wei, Gang" <gang.wei@intel.com>
Subject: Re: [PATCH 0/2] range timer support
Date: Tue, 28 Oct 2008 10:54:18 +0000	[thread overview]
Message-ID: <C52C9FDA.28751%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49582C73AC36CC4C8C6C42390304E81C092F97F902@pdsmsx502.ccr.corp.intel.com>

On 28/10/08 06:57, "Yu, Ke" <ke.yu@intel.com> wrote:

> The major changes are:
> - rebase with latest upstream: sync with the timer link list chagne (changeset
> 18381), sync with the heap memory allocation change (changeset 18671)
> - 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 original deferrable timer is renamed to range timer, to better describe
> the conecpt. This renaming is inspired by a similar proposal in linux kernel
> community (http://kerneltrap.org/mailarchive/linux-kernel/2008/9/1/3160404)
> 
> A preliminary measurement is done in a dual core mobile platform (Montivina).
> When creating 4 RHEL5 HVM UP guests, the range timer patch can reduce ~5%
> power consumption. More measurement is onging. This post is inteneded to get
> more feedback to refine it.

You'll have to explain how the implementation in timer.c works. I'm not sure
I believe it really does.

 -- Keir

  reply	other threads:[~2008-10-28 10:54 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 [this message]
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
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=C52C9FDA.28751%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=gang.wei@intel.com \
    --cc=jinsong.liu@intel.com \
    --cc=ke.yu@intel.com \
    --cc=kevin.tian@intel.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.