From: Pavel Machek <pavel@suse.cz>
To: Alok Kataria <akataria@vmware.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Dan Hecht <dhecht@vmware.com>, Tim Mann <mann@vmware.com>,
Zachary Amsden <zach@vmware.com>, Sahil Rihan <srihan@vmware.com>
Subject: Re: [RFC PATCH] x86:Use cpu_khz for loops_per_jiffy calculation
Date: Wed, 4 Jun 2008 16:17:15 +0200 [thread overview]
Message-ID: <20080604141714.GA6140@ucw.cz> (raw)
In-Reply-To: <1212540069.19290.57.camel@promb-2n-dhcp368.eng.vmware.com>
Hi!
> @@ -123,6 +123,8 @@
> (boot_cpu_data.x86_vendor == X86_VENDOR_AMD))
> cpu_khz = calculate_cpu_khz();
>
> + lpj_tsc = ((unsigned long)cpu_khz * 1000)/HZ;
> +
No. Some cpus do one loop per tick, some do two loops per tick, and
there are probably weird cpus, too.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-06-04 14:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 0:41 [RFC PATCH] x86:Use cpu_khz for loops_per_jiffy calculation Alok Kataria
2008-06-04 1:20 ` Arjan van de Ven
2008-06-04 4:01 ` Alok kataria
2008-06-04 13:16 ` Arjan van de Ven
2008-06-05 18:37 ` Alok Kataria
2008-06-20 1:22 ` Alok Kataria
2008-06-20 11:39 ` Ingo Molnar
2008-06-20 22:06 ` Alok Kataria
2008-06-23 20:54 ` Ingo Molnar
2008-06-23 23:21 ` Ingo Molnar
2008-06-23 23:34 ` Alok Kataria
2008-06-23 23:47 ` Ingo Molnar
2008-06-24 1:21 ` Alok Kataria
2008-06-24 11:54 ` Ingo Molnar
2008-06-24 17:57 ` Pavel Machek
2008-06-26 17:20 ` Alok Kataria
2008-06-26 17:35 ` Pavel Machek
2008-06-26 18:10 ` Alok Kataria
2008-06-26 22:16 ` Pavel Machek
2008-06-26 23:10 ` Alok Kataria
2008-06-27 8:12 ` Pavel Machek
2008-06-04 14:17 ` Pavel Machek [this message]
2008-06-09 13:11 ` Ingo Molnar
2008-06-09 17:55 ` Alok Kataria
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=20080604141714.GA6140@ucw.cz \
--to=pavel@suse.cz \
--cc=akataria@vmware.com \
--cc=dhecht@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mann@vmware.com \
--cc=mingo@elte.hu \
--cc=srihan@vmware.com \
--cc=tglx@linutronix.de \
--cc=zach@vmware.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