From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bin Gao <bin.gao@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Bin Gao <bin.gao@intel.com>
Subject: Re: [PATCH v2] x86, tsc: Add missing Baytrail frequency to the table
Date: Mon, 27 Jan 2014 12:20:02 +0200 [thread overview]
Message-ID: <20140127102002.GT18029@intel.com> (raw)
In-Reply-To: <20140125090923.GA106810@bin.fm.intel.com>
On Sat, Jan 25, 2014 at 01:09:23AM -0800, Bin Gao wrote:
> > diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c index a3acbac2ee72$
> > --- a/arch/x86/kernel/tsc.c
> > +++ b/arch/x86/kernel/tsc.c
> > @@ -655,10 +655,11 @@ unsigned long native_calibrate_tsc(void)
> > local_irq_save(flags);
> > i = try_msr_calibrate_tsc(&fast_calibrate);
> > local_irq_restore(flags);
> > - if (i >= 0) {
> > - if (i == 0)
> > - pr_warn("Fast TSC calibration using MSR failed\n");
> > + if (i > 0) {
> > return fast_calibrate;
> > + } else if (i == 0) {
> > + pr_warn("Fast TSC calibration using MSR failed\n");
> > + /* Continue with the normal calibration */
> > }
> >
> > local_irq_save(flags);
>
> The original design is to avoid trying PIC because touching PIC on
> a non-PIC SoC will simply cause system hang. Returning 0 will cause
> kernel to mark TSC unstable(rating 0). Since PM timer and HPET are
> typically not available on non-PIC SoC, kernal falls back to jiffies
> as clock source. Developers will start looking into the TSC clibrating
> failure once they notice the jiffies clock source.
>
> >[<ffffffff810aecb0>] clockevents_config_and_register+0x20/0x30
> >[<ffffffff81030168>] setup_APIC_timer+0xc8/0xd0
> >[<ffffffff81d1104f>] setup_boot_APIC_clock+0x4cc/0x4d8
> >[<ffffffff81d0f5de>] native_smp_prepare_cpus+0x3dd/0x3f0
> >[<ffffffff81d02ee9>] kernel_init_freeable+0xc3/0x205
> >[<ffffffff8177c910>] ? rest_init+0x90/0x90
> >[<ffffffff8177c91e>] kernel_init+0xe/0x120
> >[<ffffffff8178deec>] ret_from_fork+0x7c/0xb0
> >[<ffffffff8177c910>] ? rest_init+0x90/0x90
>
> This is because kernel is trying to use tsc-deadline mode for lapic
> timer. I think the right fix is to unset X86_FEATURE_TSC_DEADLINE_TIMER
> when try_msr_calibrate_tsc() returns 0.
You are right, that works too:
[ 0.000000] Resolved frequency ID: 0, frequency: 0 KHz
[ 0.000000] tsc: Fast TSC calibration using MSR failed
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1833.334 MHz processor
If there are no objections, I can send a new version of the patch with this
fixed.
next prev parent reply other threads:[~2014-01-27 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 11:04 [PATCH] x86, tsc: Add missing Baytrail frequency to the table Mika Westerberg
2014-01-23 15:09 ` One Thousand Gnomes
2014-01-23 15:30 ` H. Peter Anvin
2014-01-23 15:35 ` Mika Westerberg
2014-01-24 8:46 ` [PATCH v2] " Mika Westerberg
[not found] ` <4460FA1017EA3844B646E90DA4E984057D5A4E9F@ORSMSX103.amr.corp.intel.com>
2014-01-25 9:09 ` Bin Gao
2014-01-27 10:20 ` Mika Westerberg [this message]
2014-01-28 12:04 ` Mika Westerberg
2014-01-29 21:47 ` Bin Gao
2014-02-04 13:28 ` Mika Westerberg
2014-02-06 5:44 ` Ingo Molnar
2014-02-06 11:49 ` [PATCH v3 1/2] x86, tsc: Fallback to normal calibration if fast MSR calibration fails Mika Westerberg
2014-02-06 11:49 ` [PATCH v3 2/2] x86, tsc: Add missing Baytrail frequency to the table Mika Westerberg
2014-02-06 14:34 ` [PATCH v3 1/2] x86, tsc: Fallback to normal calibration if fast MSR calibration fails Thomas Gleixner
2014-02-06 15:11 ` Mika Westerberg
2014-02-09 14:20 ` Ingo Molnar
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=20140127102002.GT18029@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bin.gao@intel.com \
--cc=bin.gao@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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).