From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [RFC PATCH V2 4/4] Utilize the vmx preemption timer for tsc deadline timer Date: Wed, 25 May 2016 15:38:57 +0200 Message-ID: <20160525133857.GB14795@potion> References: <1464128852-14138-1-git-send-email-yunhong.jiang@linux.intel.com> <1464128852-14138-5-git-send-email-yunhong.jiang@linux.intel.com> <3d6068c4-34b8-fe23-9107-13eac6be0b41@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Matlack , Yunhong Jiang , kvm list , Marcelo Tosatti , Wanpeng Li To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:34703 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750779AbcEYNjB (ORCPT ); Wed, 25 May 2016 09:39:01 -0400 Content-Disposition: inline In-Reply-To: <3d6068c4-34b8-fe23-9107-13eac6be0b41@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 2016-05-25 12:40+0200, Paolo Bonzini: > On 25/05/2016 01:11, David Matlack wrote: >> > However, it possibly has impact if the vCPU thread is scheduled in/out >> > very frequently, because it switches from/to the hrtimer emulation a lot. >> >> What is the cost of the extra sched-in/out hooks? > > I still have to review this version of the patches, but I think they can > be removed and moved to blocking/unblocking instead. I this so as well. hrtimer does not make a difference to a preempted VCPU or VCPU in userspace, only the blocking sleep needs to be interrupted.