From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 4/4] KVM: x86: track actual TSC frequency from the timekeeper struct Date: Fri, 19 Feb 2016 16:53:42 +0100 Message-ID: <56C73A86.8040309@redhat.com> References: <1454944711-33022-1-git-send-email-pbonzini@redhat.com> <1454944711-33022-5-git-send-email-pbonzini@redhat.com> <20160216134816.GA21944@amt.cnet> <20160216142544.GA23955@amt.cnet> <56C3558D.2020008@redhat.com> <20160219141203.GC3956@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit To: Marcelo Tosatti , KVM list , "linux-kernel@vger.kernel.org" Return-path: In-Reply-To: <20160219141203.GC3956@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 19/02/2016 15:12, Marcelo Tosatti wrote: > >> > I need to check how often the timekeeper updates the parameters. > I'd assume once every tick, the function is called (the notifier). > > But you can optimize that away by only updating the TSC frequency > when mult/shift are updated, which should be much rarer. Yes, exactly. That would still not be rate limiting. But worst case it can be a lot of adjustments, up to HZ per second... Paolo