From: Andrew Morton <akpm@osdl.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386 Time: Avoid PIT SMP lockups
Date: Wed, 11 Oct 2006 14:26:46 -0700 [thread overview]
Message-ID: <20061011142646.eb41fac3.akpm@osdl.org> (raw)
In-Reply-To: <1160596462.5973.12.camel@localhost.localdomain>
On Wed, 11 Oct 2006 12:54:21 -0700
john stultz <johnstul@us.ibm.com> wrote:
> Andrew: I think this is 2.6.19 material, but probably should go through an -mm or two.
>
> thanks
> -john
>
>
> This patch avoids possible PIT livelock issues seen on SMP systems (and
> reported by Andi), by not allowing it as a clocksource on SMP boxes.
>
> However, since the PIT may no longer be present, we have to properly
> handle the cases where SMP systems have TSC skew and fall back from the
> TSC. Since the PIT isn't there, it would "fall back" to the TSC again.
> So this changes the jiffies rating to 1, and the TSC-bad rating value to
> 0.
>
> Thus you will get the following behavior priority on i386 systems:
>
> tsc [if present & stable]
> hpet [if present]
> cyclone [if present]
> acpi_pm [if present]
> pit [if UP]
> jiffies
>
> Rather then the current more complicated:
> tsc [if present & stable]
> hpet [if present]
> cyclone [if present]
> acpi_pm [if present]
> pit [if cpus < 4]
Actually <=4, and that matters: there are a lot of 4-ways.
> tsc [if present & unstable]
> jiffies
>
So this patch has the potential to screw up people who have 2-way or 4-way,
no hpet/pm-timer and dodgy TSCs.
Wouldn't it be better to fix the livelock? What's causing it?
next prev parent reply other threads:[~2006-10-11 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 19:54 john stultz
2006-10-11 21:26 ` Andrew Morton [this message]
2006-10-11 22:48 ` john stultz
2006-10-11 23:03 ` Andrew Morton
2006-10-16 13:48 ` Andi Kleen
2006-10-16 18:39 ` Andrew Morton
2006-10-16 18:42 ` Andi Kleen
2006-10-16 19:09 ` john stultz
2006-10-18 16:16 ` Maciej W. Rozycki
2006-10-18 16:27 ` Andi Kleen
2006-10-18 16:45 ` Maciej W. Rozycki
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=20061011142646.eb41fac3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®