All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Kevin Tian <kevin.tian@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: cpufreq status information
Date: Mon, 08 Sep 2008 15:23:54 +0100	[thread overview]
Message-ID: <48C5519A.76E4.0078.0@novell.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F024D9765@pdsmsx412.ccr.corp.intel.com>

>>> "Tian, Kevin" <kevin.tian@intel.com> 08.09.08 15:50 >>>
>>From: Jan Beulich [mailto:jbeulich@novell.com] 
>>How? I can't see where the current frequency a CPU is running at
>>is being exposed.
>
>common/sysctl.c: XEN_SYSCTL_get_pmstat

Ah, okay, I missed that. But - I can't use this from the kernel anyway,
and tools that track the frequency (i.e. KDE sysguard) would need to
be modified in order to make use of this. I'd really prefer /proc/cpuinfo
to correctly reflect this at least in Dom0. And even beyond that - I can't
seem to find any users of the APIs in tools/libxc/xc_pm.c, so these
really appear to be dead stubs.

>Then you have to pin dom0 vCPU to corresponding pCPU, and have
>dom0 with same number as pCPU. I don't think such limitation
>necessary for just retrieving some pCPU information.
>
>Or if you still enable vcpu migration, you have to fake virtual freq
>change notification within dom0 at vcpu migration as pCPU may 
>scale its own freq individually.

Why? All I care about is a snapshot value. It doesn't matter whether
it's stale by the time I get it, there's nothing going to be calculated
from it, apart from statistics.

Jan

  parent reply	other threads:[~2008-09-08 14:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 13:12 cpufreq status information Jan Beulich
2008-09-08 13:22 ` Tian, Kevin
2008-09-08 13:33   ` Jan Beulich
2008-09-08 13:50     ` Tian, Kevin
2008-09-08 14:00       ` Keir Fraser
2008-09-08 14:13         ` Tian, Kevin
2008-09-08 14:30         ` Jan Beulich
2008-09-08 14:35           ` Keir Fraser
2008-09-08 14:49             ` Tian, Kevin
2008-09-08 15:04               ` Keir Fraser
2008-09-08 14:57           ` Tian, Kevin
2008-09-08 14:23       ` Jan Beulich [this message]
2008-09-08 14:42         ` Tian, Kevin
2008-09-08 13:38 ` 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=48C5519A.76E4.0078.0@novell.com \
    --to=jbeulich@novell.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.