linux-kernel - Re: PATCH: Allow user to force 'tsc' to be treated as stable.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LNX.1.10.0902070022190.11630@jikos.suse.cz>
Date:	Sat, 7 Feb 2009 00:24:33 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Ben Greear <greearb@...delatech.com>
cc:	linux-kernel <linux-kernel@...r.kernel.org>, rusty@...tcorp.com.au
Subject: Re: PATCH:  Allow user to force 'tsc' to be treated as stable.

On Fri, 6 Feb 2009, Ben Greear wrote:

> > How do you know that the TSC is stable on such system? What was the 
> > reason for kernel marking it unstable?
> I've used it for a timing source in my own modules and it has worked 
> well.  It could still be broken in some way, but if so, I'm not sure how 
> to detect it.  Ingo sent me a program to test the tsc, and at least for 
> short runs, it showed no problem.
> Another person suggested the system might think it is unstable because I 
> have ACPI disabled in my BIOS and that might cause the kernel not to 
> have a 'PM timer' that it uses to check the tsc?
> Other than that, I have no idea why the kernel thinks the tsc is 
> unstable.

Normally the reason should be indicated by kernel in dmesg output, could 
you please provide that?

Thanks,

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