All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "solsTiCe d'Hiver" <solstice.dhiver@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6
Date: Tue, 10 Jun 2008 13:42:02 -0700	[thread overview]
Message-ID: <484EE71A.40002@intel.com> (raw)
In-Reply-To: <20080610131314.5f7069e6@infradead.org>

Arjan van de Ven wrote:
> On Tue, 10 Jun 2008 21:52:23 +0200
> solsTiCe d'Hiver <solstice.dhiver@gmail.com> wrote:
> 
>> hi,
>>
>> i am running a 2.6.25.5-rt6 kernel.
>> i know there is no such thing as 2.6.25.5-rt6 yet. so i have checked
>> with a 2.6.25.4-rt6 kernel and i have the same issue.
>>
>> when i try to run jackd (0.109.2) i get that strange error:
>> FATAL: cannot locate cpu MHz in /proc/cpuinfo
>>
>> and it appears that /proc/cpuinfo lack the line 
>> cpu MHz:
> 
> 
> btw this is scary; the Mhz line in /proc/cpuinfo doesn't have much
> meaning really, so applications using it and depending on it is a
> rather big disaster ;-(
> 
> Does anyone know why jackd wants to use this?

I just poked into Jackd and it seems to be using fallback code to calculate timing
intervals from the cpu MHz value (config/os/gnu-linux/time.c).

the code itself is self-addmittedly a kludge:


122 /*
123  * This is another kludge.  It looks CPU-dependent, but actually it
124  * reflects the lack of standards for the Linux kernel formatting of
125  * /proc/cpuinfo.
126  */
127
128 jack_time_t
129 jack_get_mhz (void)
130 {
131         FILE *f = fopen("/proc/cpuinfo", "r");

one kludge building on another :)


Auke


  reply	other threads:[~2008-06-10 20:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:52 PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6 solsTiCe d'Hiver
2008-06-10 20:13 ` Arjan van de Ven
2008-06-10 20:42   ` Kok, Auke [this message]
2008-06-11 12:42     ` Jan Engelhardt
2008-06-11 13:36       ` Arjan van de Ven
2008-06-11 13:52         ` Jan Engelhardt
2008-06-11 13:58           ` Arjan van de Ven
2008-06-11 14:14             ` linux-os (Dick Johnson)
2008-06-11 15:10               ` Peter Zijlstra
2008-06-11 15:36               ` Arjan van de Ven
2008-06-11 16:59                 ` Mark Hounschell
2008-06-11 17:44                   ` Arjan van de Ven
2008-06-11 17:54                     ` Mark Hounschell
2008-06-11 20:29                       ` Arjan van de Ven
2008-06-11 20:37                       ` Mark Hounschell
2008-06-11 20:55                         ` Arjan van de Ven
2008-06-11 20:59                           ` Mark Hounschell
2008-06-11 20:58                         ` Arjan van de Ven
2008-06-11 21:08                           ` Mark Hounschell
2008-06-11 21:28                             ` Arjan van de Ven
2008-06-11 21:39                             ` Chris Friesen
2008-06-11 23:08                       ` Andi Kleen
2008-06-11 16:08         ` Ray Lee
2008-06-11 16:32           ` Arjan van de Ven
2008-06-11 12:40 ` Jan Engelhardt
2008-06-11 14:15   ` solsTiCe d'Hiver
2008-06-11 14:36     ` Jan Engelhardt
2008-06-11 15:35       ` solsTiCe d'Hiver

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=484EE71A.40002@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solstice.dhiver@gmail.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.