From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755318AbcEZUmB (ORCPT ); Thu, 26 May 2016 16:42:01 -0400 Received: from mga03.intel.com ([134.134.136.65]:17007 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754386AbcEZUl7 (ORCPT ); Thu, 26 May 2016 16:41:59 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,370,1459839600"; d="scan'208";a="709450711" Date: Thu, 26 May 2016 13:33:31 -0700 From: yunhong jiang To: Paolo Bonzini Cc: Wanpeng Li , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Wanpeng Li , Radim =?UTF-8?B?S3LEjW3DocWZ?= , David Matlack , Christian Borntraeger , Yang Zhang Subject: Re: [PATCH v5] KVM: halt-polling: poll for the upcoming fire timers Message-ID: <20160526133331.5aadf122@jnakajim-build> In-Reply-To: References: <1464144467-6714-1-git-send-email-wanpeng.li@hotmail.com> Organization: otc X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 May 2016 12:26:27 +0200 Paolo Bonzini wrote: > > > On 25/05/2016 04:47, Wanpeng Li wrote: > > From: Wanpeng Li > > > > If an emulated lapic timer will fire soon(in the scope of 10us the > > base of dynamic halt-polling, lower-end of message passing workload > > latency TCP_RR's poll time < 10us) we can treat it as a short halt, > > and poll to wait it fire, the fire callback apic_timer_fn() will set > > KVM_REQ_PENDING_TIMER, and this flag will be check during busy poll. > > This can avoid context switch overhead and the latency which we wake > > up vCPU. > > As discussed on IRC, I would like to understand why the adaptive Glad to know the IRC channel. Is #kvm channel on freenode the IRC you are talking about? Thanks --jyh