From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [RFC] fix VMX TSC synchronicity Date: Wed, 16 Jan 2008 06:51:59 +0100 Message-ID: References: <20080111204933.GA28318@dmt> <478A01D1.7000402@qumranet.com> <20080114160647.GA15919@dmt> <478CC448.1030901@qumranet.com> <478CC819.3040106@csgraf.de> <478CCCA9.2080300@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Alexander Graf , kvm-devel To: Avi Kivity Return-path: In-Reply-To: <478CCCA9.2080300-atKUWr5tajBWk0Htik3J/w@public.gmane.org> (Avi Kivity's message of "Tue\, 15 Jan 2008 17\:09\:29 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity writes: > Thanks; that's reassuring to know that it will work (at least on Intel). Actually there are modern Intel systems which still have instable TSCs; e.g. IBM Summit multi node systems and some others. So you should still handle that case. -Andi ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/