From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by dpdk.org (Postfix) with ESMTP id BEF4D595B for ; Sat, 22 Nov 2014 18:06:31 +0100 (CET) Received: by mail-wi0-f173.google.com with SMTP id r20so2051289wiv.6 for ; Sat, 22 Nov 2014 09:17:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OM9nl2NjkVpXkIuguVbkbUdVD4us36I11+Pk88yurho=; b=GgU9DGFRoZ7j/kud/MobA/GvFiG7liaxWrgUgM1tcBiecad/Spm8IoKTMKy5bArNKJ rhf3VV0qrG4CC2xkSkxi6enXXeccnKG8weSjnx1zOHkWPP5R68gJV07lJGrMSIqpwOQK OhCOYnU97GidiBTovvAYT60MOwKz9Q8Nlx1ycuAgQnk1fNZtZZ50ukCrnfC0leVaoz2E KcL92yAXuTc4QZTODlm0gJnVN58BewtfHQYpQNTcB3MutmzlxalNEcZA76ShnxQLTYSz d34u7RPJoOEjWjB2Ko2rfUOgrDu/+RRdmu+1GWlw1DHl0RKztz49ID3UFXkoHP2YDZra F65Q== X-Gm-Message-State: ALoCoQl+6gJnK8WVXTqDvj95CAw6UtfrSA4/7AoJEYDefYCBz9Adwi1fhxARrGlOMyIru5IXFhTw X-Received: by 10.194.61.115 with SMTP id o19mr19435927wjr.12.1416676631011; Sat, 22 Nov 2014 09:17:11 -0800 (PST) Received: from saturne.dev.6wind.com (bzq-164-168-31-202.red.bezeqint.net. [31.168.164.202]) by mx.google.com with ESMTPSA id t9sm12912496wjf.41.2014.11.22.09.17.08 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 22 Nov 2014 09:17:10 -0800 (PST) Message-ID: <5470C514.3080307@6wind.com> Date: Sat, 22 Nov 2014 18:17:08 +0100 From: Vincent JARDIN Organization: www.6wind.com User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: "dev@dpdk.org" , "qemu-devel@nongnu.org Developers" 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> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4BD63@IRSMSX102.ger.corp.intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini 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: Sat, 22 Nov 2014 17:06:32 -0000 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