mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, perfmon@napali.hpl.hp.com
Subject: Re: exposing FSB clock speed in /sys
Date: Fri, 30 Mar 2007 08:49:52 -0700	[thread overview]
Message-ID: <1175269792.3360.2.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070330153937.GC16059@frankl.hpl.hp.com>

On Fri, 2007-03-30 at 07:39 -0800, Stephane Eranian wrote:
> Hello,
> 
> It seems that the kernel does not expose the Front-Side Bus (FSN) Clock
> speed to user applications

and that is a good thing ;)



> Knowledge the the FSB speed is very useful to monitoring tools. It is used
> to compute certain bus-related metrics.

perhaps. 
> 
> 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.

... yet not all CPU's *have* an FSB. Notably AMD ones do not, and I'm
sure you've read on a lot of online tech magazines that other vendors
may also not have one in the future  :-)

Exposing a concept that we KNOW does not make sense via a kernel
interface (which means we need to keep it around forever) is in my
opinion quite a bad mistake to make.... Please lets not do this.




  reply	other threads:[~2007-03-30 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 15:39 Stephane Eranian
2007-03-30 15:49 ` Arjan van de Ven [this message]
2007-03-30 18:20 ` Alan Cox
2007-03-30 18:44 ` [perfmon] " Martin Cracauer
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=1175269792.3360.2.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.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

all inboxes | Powered by JetHome®