From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755100AbbERWj5 (ORCPT ); Mon, 18 May 2015 18:39:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55535 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753333AbbERWjy (ORCPT ); Mon, 18 May 2015 18:39:54 -0400 Date: Mon, 18 May 2015 19:39:36 -0300 From: Marcelo Tosatti To: Sasha Levin Cc: KVM General , LKML , Paolo Bonzini , lcapitulino@redhat.com Subject: Re: kvm: odd time values since "kvmclock: set scheduler clock stable" Message-ID: <20150518223936.GA4486@amt.cnet> References: <55528A04.2060404@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55528A04.2060404@oracle.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 12, 2015 at 07:17:24PM -0400, Sasha Levin wrote: > Hi all, > > I'm seeing odd jump in time values during boot of a KVM guest: > > [...] > [ 0.000000] tsc: Detected 2260.998 MHz processor > [3376355.247558] Calibrating delay loop (skipped) preset value.. > [...] > > I've bisected it to: Paolo, Sasha, Although this might seem undesirable, there is no requirement for sched_clock to initialize at 0: " * * There is no strict promise about the base, although it tends to start * at 0 on boot (but people really shouldn't rely on that). * " Sasha, are you seeing any problem other than the apparent time jump?