xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: James Dingwall <james@dingwall.me.uk>
To: xen-devel@lists.xen.org
Subject: [james-xen@dingwall.me.uk: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling]
Date: Sun, 30 Sep 2012 17:13:45 +0100	[thread overview]
Message-ID: <20120930161345.GA31109@dingwall.me.uk> (raw)

Hi,

I didn't get any response on xen-users for this issue but so I'm hoping 
-devel can help.

I have had problems using cpu frequency scaling since the 
xen-acpi-processor code was added to the mainline kernel source.  I 
wasn't sure if the problem I was seeing was related to the old version 
(4.1.2) of Xen that I was using but now I'm on 4.2.0 and it still exists 
I thought I would check if I have a misconfiguration or if I have 
discovered a problem.  My system is a dual AMD Opteron(tm) Processor 
2423 HE on kernel 3.4.8.

The xen command line is:
 console=vga,com2 com2=115200,8n1 dom0_mem=max:2048M dom0_max_vcpus=2
dom0_vcpus_pin

The CPU scaling information reported by xenpm is below.  The problem
is that only cpuid 1 can be managed separately, all the others are
bundled together and cannot be handled independently which used to be
possible with the old xen kernel.  If further information would be
useful please let me know.

Thanks,
James

# xenpm get-cpufreq-para
cpu id               : 0
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 1
affected_cpus        : 1
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 2
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 3
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 4
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 5
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 6
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 7
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 8
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 9
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 10
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

cpu id               : 11
affected_cpus        : 0 2 3 4 5 6 7 8 9 10 11
cpuinfo frequency    : max [2000000] min [800000] cur [800000]
scaling_driver       :
scaling_avail_gov    : userspace performance powersave ondemand
current_governor     : ondemand
  ondemand specific  :
    sampling_rate    : max [10000000] min [10000] cur [20000]
    up_threshold     : 80
scaling_avail_freq   : 2000000 1500000 1300000 1000000 *800000
scaling frequency    : max [2000000] min [800000] cur [800000]

             reply	other threads:[~2012-09-30 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30 16:13 James Dingwall [this message]
2012-10-01 16:33 ` [james-xen@dingwall.me.uk: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling] Konrad Rzeszutek Wilk
2012-10-01 20:27   ` James Dingwall
2012-10-02 19:08     ` Konrad Rzeszutek Wilk
2012-10-02 21:30       ` James Dingwall

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=20120930161345.GA31109@dingwall.me.uk \
    --to=james@dingwall.me.uk \
    --cc=xen-devel@lists.xen.org \
    /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).