linux-kernel - Re: [PATCH] x86: don't compile vsmp

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: <20090326091153.GB9369@elte.hu>
Date:	Thu, 26 Mar 2009 10:11:53 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Ravikiran G Thirumalai <kiran@...lex86.org>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	shai@...lex86.org
Subject: Re: [PATCH] x86: don't compile vsmp_64 for 32bit


* Ravikiran G Thirumalai <kiran@...lex86.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/