From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [RFC PATCH v2 2/2] add support for Hyper-V invariant TSC Date: Fri, 24 May 2013 16:41:24 -0300 Message-ID: <20130524194124.GA2888@amt.cnet> References: <1368947197-9033-1-git-send-email-vrozenfe@redhat.com> <1368947197-9033-3-git-send-email-vrozenfe@redhat.com> <20130522005046.GA7589@amt.cnet> <643480794.5761686.1369207375451.JavaMail.root@redhat.com> <20130522212330.GA29387@amt.cnet> <20130523091229.GI4725@redhat.com> <20130523135338.GA15652@amt.cnet> <20130523153110.GI26157@redhat.com> <278937736.7040157.1369390276708.JavaMail.root@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Gleb Natapov , kvm@vger.kernel.org, pl@dlh.net To: Vadim Rozenfeld Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46179 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755041Ab3EXTlr (ORCPT ); Fri, 24 May 2013 15:41:47 -0400 Content-Disposition: inline In-Reply-To: <278937736.7040157.1369390276708.JavaMail.root@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, May 24, 2013 at 06:11:16AM -0400, Vadim Rozenfeld wrote: > > Is there a better option? > > > If setting TscSequence to zero makes Windows fall back to the MSR this is a > better option. > > +1 > This is why MS has two different mechanisms: > iTSC as a primary, reference counters as a fall-back. Ok, is it documented that transition iTSC valid (Sequence != 0 and != 0xFFFFFFFF) -> iTSC not valid but ref MSR valid (Sequence = 0), is a valid transition? It was not obvious for me. Can you point to documentation?