Re: [bisected] Clocksource tsc unstable git

[Thomas Gleixner]

On Fri, 5 Nov 2010, Borislav Petkov wrote:
> On Fri, Nov 05, 2010 at 05:27:49PM -0400, Markus Trippelsdorf wrote:
> > Err, 20==0x14 so it's not that much difference and it's running fine here
> > also.
> > 
> > Feel free to add:
> >     Reported-and-tested-by: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
> 
> Thanks Markus,
> 
> actually your board is not what concerns me, 20 ticks is still ok, more
> or less, but there are other machines which contain absurd values in
> there like 0x37ee or 0x1000 (a Broadcom chipset). We'll need to give a
> change like that a good run before we can be absolutely sure it doesn't
> break any machines.

If the ACPI entry is known to be flaky, shouldn't we simply err out on
the safe side and use 128 ticks in any case, which is not a really big
deal.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/