From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59957) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwHp0-0001f5-3j for qemu-devel@nongnu.org; Mon, 17 Oct 2016 19:59:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwHov-0006ul-Av for qemu-devel@nongnu.org; Mon, 17 Oct 2016 19:59:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51876) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bwHov-0006te-5e for qemu-devel@nongnu.org; Mon, 17 Oct 2016 19:59:53 -0400 Date: Mon, 17 Oct 2016 21:58:49 -0200 From: Marcelo Tosatti Message-ID: <20161017235846.GA22657@amt.cnet> References: <20161014212031.GQ3275@thinpad.lan.raisama.net> <20161017094708.GB31691@amt.cnet> <20161017145008.GA2307@potion> <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> <20161017211101.GD3275@thinpad.lan.raisama.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20161017211101.GD3275@thinpad.lan.raisama.net> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] invtsc + migration + TSC scaling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , qemu-devel@nongnu.org, kvm@vger.kernel.org On Mon, Oct 17, 2016 at 07:11:01PM -0200, Eduardo Habkost wrote: > On Mon, Oct 17, 2016 at 06:24:38PM +0200, Paolo Bonzini wrote: > > On 17/10/2016 16:50, Radim Kr=C4=8Dm=C3=A1=C5=99 wrote: > > > 2016-10-17 07:47-0200, Marcelo Tosatti: > [...] > > >> since Linux guests use kvmclock and Windows guests use Hyper-V > > >> enlightenment, it should be fine to disable 2). > >=20 > > ... and 1 too. > >=20 > > We should also blacklist the TSC deadline timer when invtsc is not > > available. Actually, a nicer fix would be to check the different=20 frequencies and scale the deadline relative to the difference.=20 This would take care of both patched and non-patched guests. On a related note, what was the goal of Radim's paravirtual deadline TSC timer? > You mean on the guest-side? On the host side, it would make > existing VMs refuse to run. >=20 > --=20 > Eduardo