From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] CPUID usage for interaction between Hypervisors and Linux. Date: Thu, 02 Oct 2008 14:29:00 +0300 Message-ID: <48E4B07C.60605@redhat.com> References: <1222881242.9381.17.camel@alok-dev1> <48E3BBC1.2050607@goop.org> <1222894878.9381.63.camel@alok-dev1> <48E3E8DE.1080602@goop.org> <48E3ECD1.30809@codemonkey.ws> <20081001214338.GD634@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Jeremy Fitzhardinge , akataria@vmware.com, Rusty Russell , Gerd Hoffmann , "H. Peter Anvin" , Ingo Molnar , the arch/x86 maintainers , LKML , "Nakajima, Jun" , Daniel Hecht , Zach Amsden , "virtualization@lists.linux-foundation.org" , "kvm@vger.kernel.org" To: Chris Wright Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44666 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752950AbYJBL3y (ORCPT ); Thu, 2 Oct 2008 07:29:54 -0400 In-Reply-To: <20081001214338.GD634@sequoia.sous-sol.org> Sender: kvm-owner@vger.kernel.org List-ID: Chris Wright wrote: > * Anthony Liguori (anthony@codemonkey.ws) wrote: > >> And arguably, storing TSC frequency in CPUID is a terrible interface >> because the TSC frequency can change any time a guest is entered. It >> > > True for older hardware, newer hardware should fix this. I guess the > point is, the are numbers that are easy to measure incorrectly in guest. > Doesn't justify the whole thing.. > It's not fixed for newer hardware. Larger systems still have multiple tsc frequencies. -- error compiling committee.c: too many arguments to function