linux-kernel - Re: [PATCH] x86: Export tsc related information in sysfs

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: <20100518112509.GD22675@basil.fritz.box>
Date:	Tue, 18 May 2010 13:25:10 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andi Kleen <andi@...stfloor.org>,
	Venkatesh Pallipadi <venki@...gle.com>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	chris.mason@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Export tsc related information in sysfs

On Tue, May 18, 2010 at 11:58:18AM +0200, Peter Zijlstra wrote:
> On Sun, 2010-05-16 at 22:06 -0700, Arjan van de Ven wrote:
> > look we're not disabling ring 3 tsc. We could, but we don't.
> 
> Maybe we should.

That would kill the vsyscall too. Remember it's running in ring 3.

That is in theory you could disable it on systems where the vsyscall
doesn't use it, but then you would likely break huge amounts of software, 
unless you emulate it.

Emulation would be a possibility, but I'm not sure it would
make anyone really happy. It would be certainly slow.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/