All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: johnstul@us.ibm.com, jim.cromie@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Fw: Re: 2.6.17-rc1-mm1 - detects buggy TSC on GEODE
Date: Sat, 8 Apr 2006 10:43:22 -0600	[thread overview]
Message-ID: <20060408164322.GF17356@cosmic.amd.com> (raw)
In-Reply-To: <20060407174129.67e0bc45.akpm@osdl.org>

On 07/04/06 17:41 -0700, Andrew Morton wrote:
> 
> Sorry, I should have cc'ed you on this :(
 
No worries. 

> > > 1.   the new kernel is now detecting the buggy TSC on the GEODE-sc1100
> > > 2.    the bug is apparently correctable by passing 'idle=poll' on kernel 
> > > boot-line.

I am assuming that this is the problem where the TSC doesn't roll over
correctly on the SC1100 and SC1200.

> > John, does this mean that enable-tsc-for-amd-geode-gx-lx.patch is only safe
> > to merge after all your time-management patches have gone in?

If that is the case, then the enable-tsc-for-amd-geode-gx-lx.patch is still
safe since the TSC on the GX and LX doesn't have that same problem.

For what its worth, we used to have a fix for the TSC issue back
in the 2.4 days that looked something like this:

#ifdef CONFIG_GEODE_SC1200
#define rdtsc(low,high) \
	__asm__ __volatile__("rdtsc" : "=a" (low), "=d" (high)); \
	if ((unsigned long) low > 0xFFFFFFFC) high--
#else
#define rdtsc(low,high) \
	__asm__ __volatile__("rdtsc" : "=a" (low), "=d" (high))
#endif

That seemed to work, but it is ugly, and I didn't bring it forward
when we moved to 2.6.  Perhaps we can revive it if there are SC1100/SC1200
users who need it.

Thanks,
Jordan

-- 
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>


           reply	other threads:[~2006-04-08 16:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20060407174129.67e0bc45.akpm@osdl.org>]

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=20060408164322.GF17356@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=akpm@osdl.org \
    --cc=jim.cromie@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.