public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Cracauer <cracauer@cons.org>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: linux-kernel@vger.kernel.org, perfmon@napali.hpl.hp.com
Subject: Re: [perfmon] exposing FSB clock speed in /sys
Date: Fri, 30 Mar 2007 14:44:39 -0400	[thread overview]
Message-ID: <20070330184439.GA6671@cons.org> (raw)
In-Reply-To: <20070330153937.GC16059@frankl.hpl.hp.com>

Stephane Eranian wrote on Fri, Mar 30, 2007 at 07:39:37AM -0800: 
> Hello,
> 
> It seems that the kernel does not expose the Front-Side Bus (FSN) Clock
> speed to user applications. I found code in the kernel dealing with
> frequency scaling that extracts the information for x86 processors but
> the value is never exposed.
> 
> Knowledge the the FSB speed is very useful to monitoring tools. It is used
> to compute certain bus-related metrics.
> 
> Looking at the code, it seems that there is no standard way of extracting
> the FSB speed. For each processor model, you have different MSRs. I would
> think that the routines in the cpufreq code could be moved out and used
> as the basis to expose the information somewhere in /sys.

That is still problematic as finding out the FSB might not be
trivial.  For example, for the NForce4 chipsets we have a too to
manipulate FSB and multipliers, but it's not in the kernel and never
will be.  I don't think that K8 has a way to find the FSB from the CPU
only, so you are bound to tangle with "nice" chipsets from NVidia et al.

I like the idea, but I expect there will be reservations against
presenting a /proc file that cannot be supported for almost all
machines. 

In general, I would like the cpufreq code split up, as I need to reuse
parts of it for other clock manipulation projects.  Currently, cpufreq
is a blob of code to manipulate frequencies, and to deal with the
fallout.  These two should be split up.

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org>   http://www.cons.org/cracauer/
FreeBSD - where you want to go, today.      http://www.freebsd.org/

  parent reply	other threads:[~2007-03-30 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 15:39 exposing FSB clock speed in /sys Stephane Eranian
2007-03-30 15:49 ` Arjan van de Ven
2007-03-30 18:20 ` Alan Cox
2007-03-30 18:44 ` Martin Cracauer [this message]
2007-03-31  2:31 ` Andi Kleen
2007-03-31  8:18   ` Stephane Eranian
2007-03-31 10:02     ` Andi Kleen
2007-04-02 16:14     ` Lennart Sorensen
2007-04-02 20:52       ` Stephane Eranian

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=20070330184439.GA6671@cons.org \
    --to=cracauer@cons.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfmon@napali.hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox