Received: by 10.223.164.202 with SMTP id h10csp3482452wrb; Sun, 19 Nov 2017 23:19:09 -0800 (PST) X-Google-Smtp-Source: AGs4zMYZgJNkfQug/ZoDHJNtPwEz8fg3IwqD2GgO4KVFvM52LfsvIKquu/bNcJAuyi9YRLEQMa9m X-Received: by 10.101.81.6 with SMTP id f6mr12931401pgq.64.1511162348999; Sun, 19 Nov 2017 23:19:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511162348; cv=none; d=google.com; s=arc-20160816; b=cs1wjry+3x3v6TfMhlR2u7OukOuf/VN7oeSTJ6sxzCjlO55X0Sm3bj32EcNKTr2zbr Tg7lvxWUKxJwcCpyXuAnSyMfJk6F3mz3h1cMDOqH/0tBljYeVheOnbsX1kIkjmJ3es9k ylIEywsT8Iakt0Udr/1NF7lgA+BVDzuz/ITq/jIjRRhl1jb8Mvduw4KscJqke0r9LARb QobGxbz/soG3zEj22Gls9iUOn7m5ZDqhHx5hClqm066/PSmJutU3jeTyeZc4bcjilei2 beoimwB3NSpzmbF8aIv/r+xyCWrImu5c96gkGp7xVXS+x2M1wzihg6y22OZ90a79qx7c ydYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=8xaL0RuOWIRIIG+eM2Hb3hE/skVDhJLKwrBxdSvRSoI=; b=rmRHDz84xdzVKrbI/kMGbdfvfHIOPY9XdAVy/MZkRoc3TuoycvT6WLidAkFxDNUxg1 NZGaUl9YB9nVARk50RqiEAnDQaxw3j0qZReXU+Oqc85VY/+q9aMeAyjmUIc51gqDjXe1 kQzLhqeJQ/tBFhQqhbkuJ1HsBLS0FjNab+beTVlca1mLhVpj4vKxTbtnnWRhgOYiFjrL Z6EA35LYrRbH91b6T4+xzrUsLlue1JcRR5ooH2/23BowzAr/AMaywSkAH9f/MkEUhTFJ xZKNBtg5RZtdYoopQf9amKvwvHzEmxj10JUg+VRSdA1B+KZai1qWFBGDA7CNp5WWUjuD yozw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=JxWIWm1u; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w5si7460019pfw.216.2017.11.19.23.18.58; Sun, 19 Nov 2017 23:19:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=JxWIWm1u; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751092AbdKTHSV (ORCPT + 68 others); Mon, 20 Nov 2017 02:18:21 -0500 Received: from mail-oi0-f68.google.com ([209.85.218.68]:33003 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750795AbdKTHSS (ORCPT ); Mon, 20 Nov 2017 02:18:18 -0500 Received: by mail-oi0-f68.google.com with SMTP id f135so5551100oib.0; Sun, 19 Nov 2017 23:18:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=8xaL0RuOWIRIIG+eM2Hb3hE/skVDhJLKwrBxdSvRSoI=; b=JxWIWm1u3W2ssi9Qw2YD1CczLwMMzCSn1tABggZjWiqcZInz0TZwqmYoElukeURs8F r37NsAoneHvHpTCxPKhWGV0x2u8YW0H/nk9s/QOV2GD0p8G/p5dIyIn9MvlnO8eDVhSi ZKizwOG/z890VNDXA1NFpWbmaoSLWnxB4Wd9HVYuvyzOHBLbpSZsUJ3605iv6Zr7BThT S/4AqaT6ieEvp7V9j0og0zWNNtZNxUfzSMTrxdCcMRXu+WQFkU5IPkAtjQljSbuTQxOa 2i1ywdcj8UZ9heyMN35JMK6RYXWT2Scs6Iiuoe7wdOYf1CIy8e6QryTHBz7bZoSSV9W8 wnoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=8xaL0RuOWIRIIG+eM2Hb3hE/skVDhJLKwrBxdSvRSoI=; b=eYSnLaWchl3OUOoasIxFQa852WZwqlHK7r7LqfaQsdW2bDaxGZAil0bQY5mFzy7IcL c9TvkVMYp7VyTUV+rPTQeBgyqLVsaOzAMuSZTkWLQPUQs0lqYw2Tqr+w7s1n1FKd3u2i QLT2splFCmnDrraZGCEwkiKrDe0J9u/ja+XjaqbA+2Vz8mDcrR76rTDqoQZPWD542Cp8 LF+5PBUxrFJiix7uNJ2TwXfrlrUjob1sRX1AhgKVQEK9BGDN6KfjRstwS0T9CiMoK5HP cfkkb+Q+YGd0YxuptpnSd/rnDsWVytgFagXqwlwbFqis5qzFtHcEty+81bznORcWeIoM kPvg== X-Gm-Message-State: AJaThX7VVzJtSCIKwyqtjzVf8jrSnrVswvt3Ha4aGgB9jVk/dL1IJmyq 4RS8hiupOL5oLR1AOU19AzE= X-Received: by 10.202.229.140 with SMTP id c134mr6549412oih.59.1511162298248; Sun, 19 Nov 2017 23:18:18 -0800 (PST) Received: from [0.0.0.0] ([47.89.242.186]) by smtp.gmail.com with ESMTPSA id x127sm4204542oix.8.2017.11.19.23.18.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Nov 2017 23:18:17 -0800 (PST) Subject: Re: [Xen-devel] [PATCH RFC v3 0/6] x86/idle: add halt poll support To: Konrad Rzeszutek Wilk , Quan Xu Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, x86@kernel.org, xen-devel@lists.xenproject.org, Yang Zhang References: <1510567565-5118-1-git-send-email-quan.xu0@gmail.com> <20171115213131.GB21113@char.us.oracle.com> From: Quan Xu Message-ID: <3c0c8999-f4e9-d8ae-571f-b62abfe6b4e4@gmail.com> Date: Mon, 20 Nov 2017 15:18:10 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171115213131.GB21113@char.us.oracle.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017-11-16 05:31, Konrad Rzeszutek Wilk wrote: > On Mon, Nov 13, 2017 at 06:05:59PM +0800, Quan Xu wrote: >> From: Yang Zhang >> >> Some latency-intensive workload have seen obviously performance >> drop when running inside VM. The main reason is that the overhead >> is amplified when running inside VM. The most cost I have seen is >> inside idle path. > Meaning an VMEXIT b/c it is an 'halt' operation ? And then going > back in guest (VMRESUME) takes time. And hence your latency gets > all whacked b/c of this?    Konrad, I can't follow 'b/c' here.. sorry. > So if I understand - you want to use your _full_ timeslice (of the guest) > without ever (or as much as possible) to go in the hypervisor?     as much as possible. > Which means in effect you don't care about power-saving or CPUfreq > savings, you just want to eat the full CPU for snack?   actually, we  care about power-saving. The poll duration is self-tuning, otherwise it is almost as the same as   'halt=poll'. Also we always sent out with CPU usage of benchmark netperf/ctxsw. We got much more   performance with limited promotion of CPU usage. >> This patch introduces a new mechanism to poll for a while before >> entering idle state. If schedule is needed during poll, then we >> don't need to goes through the heavy overhead path. > Schedule of what? The guest or the host?   rescheduled of guest scheduler..   it is the guest. Quan Alibaba Cloud > > From 1584171731553901534@xxx Wed Nov 15 22:11:33 +0000 2017 X-GM-THRID: 1584135730404474585 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread