linux-kernel - Re: [PATCH] Re: x86_32 tsc/pit and hrtimers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0810091344250.24851@ren>
Date:	Thu, 9 Oct 2008 13:45:20 -0600 (MDT)
From:	Jeff Hansen <x@...fhansen.com>
To:	Thomas Gleixner <tglx@...utronix.de>
cc:	Chris Snook <csnook@...hat.com>, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [PATCH] Re: x86_32 tsc/pit and hrtimers

OK, so are we all agreed that something like clocksource_trust=tsc 
would be the best?

-Jeff

---------------------------------------------------
"If someone's gotta do it, it might as well be me."

On Thu, 9 Oct 2008, Thomas Gleixner wrote:

> On Thu, 9 Oct 2008, Chris Snook wrote:
>>
>> Fair enough, but do you think it's worthwhile to have an option to disable
>> CLOCK_SOURCE_MUST_VERIFY checking for all timers, or should we implement this
>> on a case-by-case basis when there's legitimate cause, like with TSC?
>
> Case-by-case is preferred.
>
> Thanks,
>
> 	tglx
>
>
--
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/