From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64: Fix CPU freq displayed in /proc/cpuinfo
Date: Fri, 06 Apr 2007 17:48:04 +0000 [thread overview]
Message-ID: <20070406174804.GA23889@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070406170449.GA21441@linux-os.sc.intel.com>
On Fri, Apr 06, 2007 at 10:29:03AM -0700, Luck, Tony wrote:
>
> + "cpu MHz : %lu.%03lu\n"
> "itc MHz : %lu.%06lu\n"
>
>
> Why did you cut the precision of cpu MHz back to 1Khz? Is the
> extra precision not-warranted, or is this just to be more like
> other architectures?
That is because we try to get this from cpufreq and cpufreq
has this info in kHz.
> Should we do the same for itc MHz to treat both evenly?
Not sure about this. I guess we can retain it the way it is as it is
something directly coming from hardware. CPU frequency in turn can come
cpufreq or acpi tables. ACPI table will reduce this further as it
always gives the info in MHz (on processors that has ACPI
based P-states support).
Thanks,
Venki
prev parent reply other threads:[~2007-04-06 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 17:04 [PATCH] ia64: Fix CPU freq displayed in /proc/cpuinfo Venki Pallipadi
2007-04-06 17:29 ` Luck, Tony
2007-04-06 17:48 ` Venki Pallipadi [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=20070406174804.GA23889@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=linux-ia64@vger.kernel.org \
/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