All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RFC: cpu frequency scaling
Date: Wed, 25 Oct 2006 14:04:08 -0400	[thread overview]
Message-ID: <453FA718.7030105@redhat.com> (raw)

Right now, CPU frequency scaling in Xen does not work (right) for a
combination of reasons:
1) dom0 might not run on all physical CPUs
2) dom0 might not even have enough VCPUs to fill all physical CPUs
3) dom0 has no idea how busy the other guests are, so it does not
    know whether to scale the CPU frequencies up or down

I can see two ways to fix this:
1) move cpu frequency scaling into the hypervisor, since the hypervisor
    knows how busy all the guests are

2) make sure every physical CPU core has a dom0 VCPU pinned to it, and
    have dom0 poll the hypervisor to find out how busy each CPU is,
    scaling the frequencies of the CPUs as required

These approaches both have their drawbacks.  One requires porting over
a series of drivers from Linux to the hypervisor, maintaining two sets
into the future.  The second could mess up some of the credit
scheduler's balancing, and requires Linux modifications to poll the
hypervisor for the CPU load...

Also, it would mean the end of running a 1 vcpu small dom0, which some
people seem to like.

Which of these approaches would you prefer?

Is there a 3rd option?

-- 
Who do you trust?
The people with all the right answers?
Or the people with the right questions?

             reply	other threads:[~2006-10-25 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 18:04 Rik van Riel [this message]
2006-10-25 20:47 ` RFC: cpu frequency scaling Keir Fraser
2006-10-25 21:13   ` Rik van Riel
2006-10-26 12:35     ` Petersson, Mats
2006-10-26 14:09       ` 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=453FA718.7030105@redhat.com \
    --to=riel@redhat.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.