Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757104AbZCZJNV (ORCPT ); Thu, 26 Mar 2009 05:13:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751522AbZCZJNM (ORCPT ); Thu, 26 Mar 2009 05:13:12 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:56325 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751294AbZCZJNL (ORCPT ); Thu, 26 Mar 2009 05:13:11 -0400 Date: Thu, 26 Mar 2009 10:11:53 +0100 From: Ingo Molnar To: Ravikiran G Thirumalai Cc: Jeremy Fitzhardinge , Yinghai Lu , Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , "linux-kernel@vger.kernel.org" , shai@scalex86.org Subject: Re: [PATCH] x86: don't compile vsmp_64 for 32bit Message-ID: <20090326091153.GB9369@elte.hu> References: <20090322124818.GA31466@elte.hu> <20090324061429.GH7278@localdomain> <20090324091035.GA6605@elte.hu> <20090325185138.GI7278@localdomain> <49CAAD2E.3060904@goop.org> <20090325223642.GK7278@localdomain> <49CABB25.8040106@goop.org> <20090325232921.GL7278@localdomain> <49CAC543.5020205@goop.org> <20090326003154.GA10614@localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090326003154.GA10614@localdomain> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 962 Lines: 28 * Ravikiran G Thirumalai wrote: > > unsynchronized_tsc() just returns a guess anyway, and if you > > don't have X86_FEATURE_CONSTANT_TSC set, then it will return > > unstable for your hardware anyway, even without the > > is_vsmp_box() test. > > Unfortunately we use hardware which has X86_FEATURE_CONSTANT_TSC. > > > > > Failing that, you could add yourself to bad_tsc_dmi_table[] and > > have that mark the tsc as unstable (you have DMI, right?). > > > > Newer versions of the VMM does, but older ones don't :(, and > obviously we have older versions out in the field that still needs > to be supported. But those old versions wont have X86_FEATURE_CONSTANT_TSC set, right? Ingo -- 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/