From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/5] Add a global synchronization point for pvclock Date: Tue, 20 Apr 2010 12:39:15 +0300 Message-ID: <4BCD7643.4000102@redhat.com> References: <1271356648-5108-1-git-send-email-glommer@redhat.com> <1271356648-5108-2-git-send-email-glommer@redhat.com> <4BCA026D.3070309@redhat.com> <1271673975.1674.763.camel@laptop> <4BCC3520.6090305@redhat.com> <1271674273.1674.777.camel@laptop> <4BCC3654.2090600@redhat.com> <4BCCA281.6040509@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Zijlstra , Glauber Costa , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Jeremy Fitzhardinge , Marcelo Tosatti To: Zachary Amsden Return-path: In-Reply-To: <4BCCA281.6040509@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 04/19/2010 09:35 PM, Zachary Amsden wrote: >>>> Sockets and boards too? (IOW, how reliable is TSC_RELIABLE)? >>> Not sure, IIRC we clear that when the TSC sync test fails, eg when we >>> mark the tsc clocksource unusable. >> >> Worrying. By the time we detect this the guest may already have >> gotten confused by clocks going backwards. > > > Upstream, we are marking the TSC unstable preemptively when hardware > which will eventually sync test is detected, so this should be fine. ENOPARSE? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.