From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 59C0E3F9 for ; Tue, 9 Dec 2014 18:35:08 +0100 (CET) Received: by mail-wi0-f179.google.com with SMTP id ex7so2523774wid.12 for ; Tue, 09 Dec 2014 09:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lubaBbHpEDBj359K1CXMupmcOciNlIgSB1tdSc6mtwY=; b=K1njGd38ViseorlFCDOHlq+TYpVj2Bo4pp/L8VgFus59hAVxgE+j3MCj+xMbMQYo7k V7tCjfgkCXBpYoDTI8tDhlb4SQG3U8KSp2zbcxZ0Qjj+9TCDu0okM6yJGKYVv+vcIyog 6TrMTwNBdRoNoDENfVkmcW/qcxK+qn9xHSRx2yGX79uLHk+Xrq9Awy1+RgzhbnIQZsQS 5dQ6Hd9WIAUwAnkGKZ1wfl6+TWJXyJFC2qB/xwtScrY18jtn+bzNVal1Y0nlSqJHDMAi 3W/kimrusNbqpvBxjH/NqmmlChVu+LTE/L31mx09KC6URguhOPVmah/JyVfPOp+IMSk1 ctdg== X-Received: by 10.194.6.7 with SMTP id w7mr6686356wjw.25.1418146508243; Tue, 09 Dec 2014 09:35:08 -0800 (PST) Received: from [192.168.10.150] (net-2-35-193-40.cust.vodafonedsl.it. [2.35.193.40]) by mx.google.com with ESMTPSA id wa5sm2615265wjc.8.2014.12.09.09.35.06 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Dec 2014 09:35:07 -0800 (PST) Sender: Paolo Bonzini Message-ID: <548732C9.2020201@redhat.com> Date: Tue, 09 Dec 2014 18:35:05 +0100 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Vincent JARDIN , dev@dpdk.org, qemu-devel References: <1412003903-9061-1-git-send-email-alan.carew@intel.com> <3349663.LNtcecTXb3@xps13> <0E29434AEE0C3A4180987AB476A6F6306D2811AD@IRSMSX109.ger.corp.intel.com> <1804867.TWdiCQc2JQ@xps13> <0E29434AEE0C3A4180987AB476A6F6306D28E7DF@IRSMSX109.ger.corp.intel.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4BD63@IRSMSX102.ger.corp.intel.com> <5470C514.3080307@6wind.com> In-Reply-To: <5470C514.3080307@6wind.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 09 Dec 2014 18:39:04 +0100 Subject: Re: [dpdk-dev] [PATCH v4 00/10] VM Power Management X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 17:35:08 -0000 I had replied to this message, but my reply never got to the list. Let's try again. I wonder if this might be papering over a bug in the host cpufreq driver. If the guest is not doing much and leaving a lot of idle CPU time, the host should scale down the frequency of that CPU. In the case of pinned VCPUs this should really "just work". What is the problem that is being solved? Paolo On 22/11/2014 18:17, Vincent JARDIN wrote: > Tim, > > cc-ing Paolo and qemu-devel@ again in order to get their take on it. > >>>> Did you make any progress in Qemu/KVM community? >>>> We need to be sync'ed up with them to be sure we share the same goal. >>>> I want also to avoid using a solution which doesn't fit with their >>>> plan. >>>> Remember that we already had this problem with ivshmem which was >>>> planned to be dropped. >>>> > >>> Unfortunately, I have not yet received any feedback: >>> http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg01103.html >> >> Just to add to what Alan said above, this capability does not exist in >> qemu at the moment, and based on there having been no feedback on the >> qemu mailing list so far, I think it's reasonable to assume that it >> will not be implemented in the immediate future. The VM Power >> Management feature has also been designed to allow easy migration to a >> qemu-based solution when this is supported in future. Therefore, I'd >> be in favour of accepting this feature into DPDK now. >> >> It's true that the implementation is a work-around, but there have >> been similar cases in DPDK in the past. One recent example that comes >> to mind is userspace vhost. The original implementation could also be >> considered a work-around, but it met the needs of many in the >> community. Now, with support for vhost-user in qemu 2.1, that >> implementation is being improved. I'd see VM Power Management >> following a similar path when this capability is supported in qemu. > > Best regards, > Vincent >