From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: invtsc + migration + TSC scaling Date: Tue, 18 Oct 2016 15:38:01 +0200 Message-ID: <20161018133800.GA3492@potion> References: <20161014212031.GQ3275@thinpad.lan.raisama.net> <20161017094708.GB31691@amt.cnet> <20161017145008.GA2307@potion> <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com> <20161018133619.GB2205@potion> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Marcelo Tosatti , Eduardo Habkost , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36214 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760068AbcJRNiF (ORCPT ); Tue, 18 Oct 2016 09:38:05 -0400 Content-Disposition: inline In-Reply-To: <20161018133619.GB2205@potion> Sender: kvm-owner@vger.kernel.org List-ID: 2016-10-18 15:36+0200, Radim Krčmář: > 2016-10-17 18:24+0200, Paolo Bonzini: >> We should also blacklist the TSC deadline timer when invtsc is not >> available. > > True. > > I was thinking that with Wanpeng's VMX preemption patches, we might not > need the TSC nor paravirtual deadline timer, the because performance of > LAPIC one-shot could be very similar. No, I sent before thinking -- deadline timer also has better precision, so it is still useful.