From: Rik van Riel <riel@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Mark Langsdorf <mark.langsdorf@amd.com>,
xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
Date: Fri, 31 Aug 2007 09:50:48 -0400 [thread overview]
Message-ID: <46D81CB8.8050904@redhat.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F013B21AE@pdsmsx412.ccr.corp.intel.com>
Tian, Kevin wrote:
> b) Code duplication is definitely bad. But if finally xen-based governor is
> proved to be with best power saving cap, why not?
Because the larger the hypervisor is, the less practical it
becomes to maintain. The current Xen hypervisor already has
bugs in its copied-from-Linux code that were fixed in Linux
after the code was copied.
A small hypervisor is nice, but Xen is painfully large to
maintain.
> d) I guess final power saving of cpufreq (either approach) is not obvious,
> since average CPU utilization should be higher than native which is the
> goal of virtualization. C-state may be more interesting.
This makes a lot of sense. C-state makes a big impact on
power usage and can be implemented inside the idle loop
relatively easily.
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
next prev parent reply other threads:[~2007-08-31 13:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 22:02 [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes Mark Langsdorf
2007-08-30 6:41 ` Tian, Kevin
2007-08-30 9:30 ` Keir Fraser
2007-08-30 9:45 ` Tian, Kevin
2007-08-30 10:12 ` Keir Fraser
2007-08-31 1:20 ` Tian, Kevin
2007-08-31 10:04 ` Keir Fraser
2007-08-31 15:09 ` Tian, Kevin
2007-08-31 15:25 ` Keir Fraser
2007-09-01 0:23 ` Tian, Kevin
2007-09-01 11:07 ` Keir Fraser
2007-09-01 13:31 ` Tian, Kevin
2007-09-01 13:57 ` Keir Fraser
2007-09-01 14:14 ` Tian, Kevin
2007-09-01 14:22 ` Tian, Kevin
2007-09-01 14:12 ` Keir Fraser
2007-09-01 14:18 ` Tian, Kevin
2007-09-01 15:26 ` Keir Fraser
2007-09-01 15:45 ` Tian, Kevin
2007-09-01 16:41 ` Keir Fraser
2007-09-03 4:25 ` Tian, Kevin
2007-09-04 17:23 ` Rik van Riel
2007-08-30 14:45 ` Langsdorf, Mark
2007-08-30 15:04 ` Keir Fraser
2007-08-30 18:23 ` Rik van Riel
[not found] ` <1449F58C868D8D4E9C72945771150BDF0207700B@SAUSEXMB1.amd.com>
2007-08-30 20:56 ` Rik van Riel
2007-08-31 2:43 ` Tian, Kevin
2007-08-31 8:41 ` Jan Beulich
2007-08-30 14:59 ` Rik van Riel
2007-08-31 2:42 ` Tian, Kevin
2007-08-31 9:23 ` Keir Fraser
2007-08-31 13:50 ` Rik van Riel [this message]
2007-08-30 14:57 ` Langsdorf, Mark
2007-08-30 15:08 ` Keir Fraser
2007-10-01 8:30 ` xeb
2007-10-01 8:33 ` Keir Fraser
2007-10-02 12:56 ` xeb
2007-10-02 12:57 ` xeb
2007-10-02 13:00 ` xeb
2007-10-02 13:02 ` xeb
-- strict thread matches above, loose matches on Subject: below --
2007-10-02 13:05 xeb
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=46D81CB8.8050904@redhat.com \
--to=riel@redhat.com \
--cc=keir@xensource.com \
--cc=kevin.tian@intel.com \
--cc=mark.langsdorf@amd.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.