From: Alok Kataria <akataria@vmware.com>
To: John Stultz <johnstul@us.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
dirk.brandewie@gmail.com, alan@linux.intel.com,
stable@kernel.org, Dan Hecht <dhecht@vmware.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, tsc: Skip refined tsc calibration on systems with reliable TSC.
Date: Tue, 28 Feb 2012 11:09:16 -0800 [thread overview]
Message-ID: <1330456156.4500.1.camel@ank32.eng.vmware.com> (raw)
In-Reply-To: <1329877195.10380.33.camel@ank32.eng.vmware.com>
Ping...any comments on this one.
Thanks,
Alok
On Tue, 2012-02-21 at 18:19 -0800, Alok Kataria wrote:
> [Oops forgot to copy LKML, now it is, sorry for the duplicates]
>
> While running the latest Linux as guest under VMware in highly
> over-committed situations, we have seen cases when the refined TSC
> algorithm fails to get a valid tsc_start value in
> tsc_refine_calibration_work from multiple attempts. As a result the
> kernel keeps on scheduling the tsc_irqwork task for later. Subsequently
> after several attempts when it gets a valid start value it goes through
> the refined calibration and either bails out or uses the new results.
> Given that the kernel originally read the TSC frequency from the
> platform, which is the best it can get, I don't think there is much
> value in refining it.
>
> So IMO, for systems which get the TSC frequency from the platform we
> should skip the refined tsc algorithm.
>
> We can use the TSC_RELIABLE cpu cap flag to detect this, right now it is
> set only on VMware and for Moorestown Penwell both of which have there
> own TSC calibration methods.
>
> Thanks,
> Alok
>
> --
>
> From: Alok N Kataria <akataria@vmware.com>
>
> For systems which get the TSC frequency directly from the platform
> and don't go through the native TSC calibration algorithm, we should
> trust those values and not try to refine those.
>
> This patch is applicable for kernel from v2.6.38 to current mainline.
>
> Signed-off-by: Alok N Kataria <akataria@vmware.com>
> Cc: John Stultz <johnstul@us.ibm.com>
> Cc: Dirk Brandewie <dirk.brandewie@gmail.com>
> Cc: Alan Cox <alan@linux.intel.com>
> Cc: stable@kernel.org
>
>
> Index: linux-2.6/arch/x86/kernel/tsc.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/tsc.c 2012-02-21 17:31:01.000000000 -0800
> +++ linux-2.6/arch/x86/kernel/tsc.c 2012-02-21 17:39:05.000000000 -0800
> @@ -874,6 +874,13 @@ static void tsc_refine_calibration_work(
> goto out;
>
> /*
> + * Trust the results of the earlier calibration on systems
> + * exporting a reliable TSC.
> + */
> + if (boot_cpu_has(X86_FEATURE_TSC_RELIABLE))
> + goto out;
> +
> + /*
> * Since the work is started early in boot, we may be
> * delayed the first time we expire. So set the workqueue
> * again once we know timers are working.
>
next prev parent reply other threads:[~2012-02-28 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329876964.10380.28.camel@ank32.eng.vmware.com>
2012-02-22 2:19 ` [PATCH] x86, tsc: Skip refined tsc calibration on systems with reliable TSC Alok Kataria
2012-02-28 19:09 ` Alok Kataria [this message]
2012-03-07 1:32 ` john stultz
2012-03-07 2:05 ` Alok Kataria
2012-03-07 3:26 ` john stultz
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=1330456156.4500.1.camel@ank32.eng.vmware.com \
--to=akataria@vmware.com \
--cc=alan@linux.intel.com \
--cc=dhecht@vmware.com \
--cc=dirk.brandewie@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).