[lkml]   [2002]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Voyager subarchitecture for 2.5.46
On Wed, 2002-11-06 at 15:03, J.E.J. Bottomley wrote:
> There are certain architectures (voyager is the only one currently supported,
> but I suspect the Numa machines will have this too) where the TSC cannot be
> used for cross CPU timings because the processors are driven by separate
> clocks and may even have different clock speeds.

IBM Summit is indeed another one.

> What I need is an option simply not to compile in the TSC code and use the PIT
> instead. What I'm trying to do with the TSC and PIT options is give three
> choices:
> 1. Don't use TSC (don't compile TSC code): X86_TSC=n, X86_PIT=y
> 2. May use TSC but check first (blacklist, notsc kernel option). X86_TSC=y,
> X86_PIT=y
> 3. TSC is always OK so don't need PIT. X86_TSC=y, X86_PIT=n

[Plus we need X86_CYCLONE and we may need X86_SOMETHING else for some
pending stuff]

> We probably need to make the notsc and dodgy tsc check contingent on X86_PIT
> (or a config option that says we have some other timer mechanism compiled in).
> Really, the options should probably be handled in timer.c.

The dodgy_tsc check is now obsolete. The known cases are handled with
workarounds and CS5510/20 can now use the TSC

> Do we have an option for a deferred panic that will trip just after we init
> the console and clean out the printk buffer?

Point to timer_none, check that later on in the boot

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:30    [W:0.086 / U:5.220 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site