From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: invtsc + migration + TSC scaling Date: Mon, 17 Oct 2016 19:11:01 -0200 Message-ID: <20161017211101.GD3275@thinpad.lan.raisama.net> References: <20161014212031.GQ3275@thinpad.lan.raisama.net> <20161017094708.GB31691@amt.cnet> <20161017145008.GA2307@potion> <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Radim =?utf-8?B?S3LEjW3DocWZ?= , Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45748 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936198AbcJQVLI (ORCPT ); Mon, 17 Oct 2016 17:11:08 -0400 Content-Disposition: inline In-Reply-To: <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Oct 17, 2016 at 06:24:38PM +0200, Paolo Bonzini wrote: > On 17/10/2016 16:50, Radim Krčmář 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). > > ... and 1 too. > > We should also blacklist the TSC deadline timer when invtsc is not > available. You mean on the guest-side? On the host side, it would make existing VMs refuse to run. -- Eduardo From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52912) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwFBc-0004pv-Lr for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:11:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwFBX-00023H-R9 for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:11:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58618) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bwFBX-00022L-Lr for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:11:03 -0400 Date: Mon, 17 Oct 2016 19:11:01 -0200 From: Eduardo Habkost Message-ID: <20161017211101.GD3275@thinpad.lan.raisama.net> References: <20161014212031.GQ3275@thinpad.lan.raisama.net> <20161017094708.GB31691@amt.cnet> <20161017145008.GA2307@potion> <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> 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: Paolo Bonzini Cc: Radim =?utf-8?B?S3LEjW3DocWZ?= , Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org 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. You mean on the guest-side? On the host side, it would make existing VMs refuse to run. --=20 Eduardo