From: Matthew Garrett <mjg@redhat.com>
To: 俞颐超 <yyc1992@gmail.com>
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: mistake about the cpufreq?
Date: Tue, 5 Jul 2011 18:55:08 +0100 [thread overview]
Message-ID: <20110705175508.GC30531@srcf.ucam.org> (raw)
In-Reply-To: <BANLkTimgadBqULuQXVdr-=e792b6RZLQSg@mail.gmail.com>
On Fri, Jul 01, 2011 at 09:17:08PM -0400, 俞颐超 wrote:
> So after reading the files in cpu-freq/, I saw it was mentioned in
> user-guide.txt that the scaling_ ones is what the kernel thinks the
> freq is and cpuinfo is the actual freq.
> y can these two be different?
Many systems don't have independently clockable cores. In that case the
cpu will run at the speed of the highest clocked core.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2011-07-05 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 20:00 mistake about the cpufreq? 俞颐超
2011-07-02 1:17 ` 俞颐超
2011-07-05 17:55 ` Matthew Garrett [this message]
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=20110705175508.GC30531@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yyc1992@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox