Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754464AbYJUBoJ (ORCPT ); Mon, 20 Oct 2008 21:44:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752191AbYJUBnk (ORCPT ); Mon, 20 Oct 2008 21:43:40 -0400 Received: from smtp-outbound-1.vmware.com ([65.115.85.69]:40106 "EHLO smtp-outbound-1.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752074AbYJUBnj (ORCPT ); Mon, 20 Oct 2008 21:43:39 -0400 Subject: [PATCH 0/3] Improve TSC as a clocksource under VMware From: Alok Kataria Reply-To: akataria@vmware.com To: "H. Peter Anvin" Cc: LKML , the arch/x86 maintainers , Dan Hecht Content-Type: text/plain Organization: VMware INC. Date: Mon, 20 Oct 2008 18:35:02 -0700 Message-Id: <1224552902.2640.88.camel@alok-dev1> Mime-Version: 1.0 X-Mailer: Evolution 2.8.0 (2.8.0-40.el5_1.1) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 722 Lines: 21 Hi, This patch set makes some changes to the TSC code, so that it is always used as the default clocksource when running under VMware. The first 2 patches do the ground work of adding code to detect if we are running under VMware. The third patch adds a tsc_reliable flag which tells us that TSC is reliable on this system, so that we can skip some tests which can potentially mark TSC as unstable. Details under individual patch headers. Please have a look. Thanks, Alok -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/