From owner-freebsd-current@freebsd.org Sun Oct 22 08:31:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C45C4E4CD49; Sun, 22 Oct 2017 08:31:26 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward105p.mail.yandex.net (forward105p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7794182929; Sun, 22 Oct 2017 08:31:26 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback9g.mail.yandex.net (mxback9g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:170]) by forward105p.mail.yandex.net (Yandex) with ESMTP id 110F74082344; Sun, 22 Oct 2017 11:31:24 +0300 (MSK) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [2a02:6b8:0:801::ab]) by mxback9g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id R6e03ZTspc-VND8iQgw; Sun, 22 Oct 2017 11:31:24 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1508661084; bh=ePzbgkEZTdPXldLnns2AnQ86wNpHyWYplqQJZziLmpU=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=glh8EbTV/dTfq46Km6J0pXzn6VlYGMtHiPl3NPgYEJLnebTYEevGKrY/SgQC2Vaou VYG9a/EJE36tmKjiZTRCFmH7E/NHSanpMaAzjnoEtNRmlwdYdHNIeXK8opN4O4zXmQ zUOMqRdt6BQDDAL5ef83kjpV/fP07/XVe22OjZvA= Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id h3FGSjBdJ3-VNZePpNo; Sun, 22 Oct 2017 11:31:23 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1508661083; bh=ePzbgkEZTdPXldLnns2AnQ86wNpHyWYplqQJZziLmpU=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=oJDo3wsGbRyOqnFL/Y/x2tGB4ije831ApS1ct2DPPg2wJRl/biWi3dHLx6sEyYgC5 GJkRvu8W+CE/tvuxP8TNQotWXdd9WcpBOE9zJT8CPZEuucdGjaExMIfVTN91xyYLH4 1eiTb7YEYaLMmTkPxUw8g5mPF1+WHIXNXmnTIlJI= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: host, bhyve vm and ntpd To: Ian Lepore , Michael Voorhis Cc: freebsd-current@FreeBSD.org, freebsd-virtualization@FreeBSD.org References: <2931f1cc-6574-b58d-4b94-5f77fa5cdb85@passap.ru> <1508512327.1383.55.camel@freebsd.org> <39bf2426-2edf-d485-7c81-519e931154be@passap.ru> <1508517160.1383.63.camel@freebsd.org> <76ff7afb-3d3a-96f6-1275-89472ff5683d@passap.ru> <1508522667.1383.69.camel@freebsd.org> <30992c14-7b78-ab9f-5693-931e6ca41f1b@passap.ru> <1508523696.1383.75.camel@freebsd.org> <23019.46875.929719.481108@atom.mcvau.net> <1508624153.1383.107.camel@freebsd.org> From: Boris Samorodov Message-ID: <6dc189a0-e7bc-6c3b-2be6-80154e7ece42@passap.ru> Date: Sun, 22 Oct 2017 11:31:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <1508624153.1383.107.camel@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Language: ru-RU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 08:31:26 -0000 22.10.2017 01:15, Ian Lepore пишет: > On Sat, 2017-10-21 at 17:07 -0400, Michael Voorhis wrote: >> Ian Lepore writes: >>> >>> Beyond that, I'm not sure what else to try.  It might be necessary to >>> get some bhyve developers involved (I know almost nothing about it). >> NTPD behaves more normally on uniprocessor VMs. >> >> A FreeBSD bhyve-guest running on a freebsd host will select a >> different timecounter depending on whether it is a multiprocessor or a >> uniprocessor.  My uniprocessor bhyve-vm selected TSC-low as the best >> timecounter in a uniprocessor.  NTP functions there as expected. >> >> kern.timecounter.choice: TSC-low(1000) ACPI-fast(900) HPET(950) i8254(0) dummy(-1000000) >> kern.timecounter.hardware: TSC-low >> >> The very same VM, when given two total CPUs, selected HPET (if I >> recall) and the timekeeping with NTPD was unreliable, with many >> step-resets to the clock. >> > > Hmm, I just had glance at the code in sys/amd64/vmm/io/vhpet.c and it > looks right.  I wonder if this is just a simple roundoff error in > converting between 10.0MHz and SBT units?  If so, that could be wished > away easily by using a power-of-2 frequency for the virtual HPET.  I > wonder if the attached patch is all that's needed? I've tried the patch (at bhyve guest) and nothing has changed. Should the patched system be tested at bhyve guest or bhyve host? -- WBR, bsam