From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757134Ab0ERL7W (ORCPT <rfc822;w@1wt.eu>);
	Tue, 18 May 2010 07:59:22 -0400
Received: from casper.infradead.org ([85.118.1.10]:45610 "EHLO
	casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756229Ab0ERL7T convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 18 May 2010 07:59:19 -0400
Subject: Re: [PATCH] x86: Export tsc related information in sysfs
From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
       Dan Magenheimer <dan.magenheimer@oracle.com>,
       Thomas Gleixner <tglx@linutronix.de>,
       Venkatesh Pallipadi <venki@google.com>, Ingo Molnar <mingo@elte.hu>,
       "H. Peter Anvin" <hpa@zytor.com>, chris.mason@oracle.com,
       linux-kernel@vger.kernel.org
In-Reply-To: <20100518112509.GD22675@basil.fritz.box>
References: <1273887635-27610-1-git-send-email-venki@google.com>
	 <87tyq9mqrz.fsf@basil.nowhere.org>
	 <35aa841b-e151-424d-b1c1-0c03dbcae5cc@default>
	 <20100515121424.38f5b389@infradead.org>
	 <e07ac2f3-4a82-41d9-aa41-49a94435e7b7@default>
	 <20100515224305.17a04022@infradead.org>
	 <alpine.LFD.2.00.1005161113450.3199@localhost.localdomain>
	 <5adf3fee-0f7b-4039-b13f-619640cc4b88@default>
	 <20100516220638.2baf315d@infradead.org> <1274176698.5605.7358.camel@twins>
	 <20100518112509.GD22675@basil.fritz.box>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Date: Tue, 18 May 2010 13:58:54 +0200
Message-ID: <1274183935.5605.7726.camel@twins>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 2010-05-18 at 13:25 +0200, Andi Kleen wrote:
> 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.

Well, software shouldn't use it, so breaking it sounds like a fine
idea ;-)

Also, a slow emulation is an incentive to actually do the right thing.