From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 2389C3256 for ; Fri, 29 Mar 2019 15:16:42 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AE39F21C6B; Fri, 29 Mar 2019 10:16:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 10:16:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=WDI5X0zPnE09j+KEhEc9qtze7Jc90MLo7K8yjkX14u8=; b=fFCGL8+PgZXC KVK0v7UPk/21ilsFjKIqwCMaD94UCY5/qk3S40khch21qdN7tDOAG3nvZj9S0SKu XhQObotmKhwL9vJdrVlplUjktU3WGr7pAlM6z8LGVriY5y+kbtq1IKWJkOLIgmDx YmzSR8cS+3jQTOFOhfj8lsYgf/NmrQE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=WDI5X0zPnE09j+KEhEc9qtze7Jc90MLo7K8yjkX14 u8=; b=Ooo87tW94hGAVguQS8qGgFQpjSGGzaGOpO/7QQBcD+O4pFqUQTG78rNXg ofHYf4/URCCSA2zxEa1M+/ibqL8dZuydLI+cOF9kPyT2zoK8IQ6LlVUa+v750Fjk ZQNOpmx6dCDowjx4UIhMX0u1EprDCfqKl0L8ENG9E50KNNBRnvQFDux6s6p8OWpj nS4M+YNiTI0sUwYHjiNWsOY2JbbQnmucXWFZMupOgHH0GxKjNsauw0T3NAQi8ZDL qMxpuN7sMO9/jKxcU9ptJWgQ0sZmDp/ccrESzK3QjwQZtvmigapDrljfAHeC2XB0 nR+42Yg/hVNtxUnfk8qPFOKkJgGfA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeejgdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrg hrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucev lhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4D07FE49E2; Fri, 29 Mar 2019 10:16:40 -0400 (EDT) From: Thomas Monjalon To: Hajkowski Cc: dev@dpdk.org, david.hunt@intel.com Date: Fri, 29 Mar 2019 15:16:38 +0100 Message-ID: <1813744.7UKQrVtjkc@xps> In-Reply-To: <20190321105506.6656-1-marcinx.hajkowski@intel.com> References: <20190321105506.6656-1-marcinx.hajkowski@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/4] bidirect guest channel X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Mar 2019 14:16:42 -0000 21/03/2019 11:55, Hajkowski: > From: Marcin Hajkowski > > Extend guest channel API to allow bidirectional > communication. Modify power manager host and guest > side to communicate in both directions. > > v3: > * fix global_fds[lcore_id] comparison to invalid value > * check 0 to verify if read function actually read some data > * define _NACK cmd instead of _NAK > * simplify rte_power_guest_channel_receive_msg func logic > > v2: > * send ack only if power operation return positive value > * log diffent error for unexpected incoming command and > error during ack/nak cmd sending Please use --in-reply-to to keep all versions in the same thread, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 088EBA05D3 for ; Fri, 29 Mar 2019 15:16:43 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CEBC43576; Fri, 29 Mar 2019 15:16:42 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 2389C3256 for ; Fri, 29 Mar 2019 15:16:42 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AE39F21C6B; Fri, 29 Mar 2019 10:16:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 10:16:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=WDI5X0zPnE09j+KEhEc9qtze7Jc90MLo7K8yjkX14u8=; b=fFCGL8+PgZXC KVK0v7UPk/21ilsFjKIqwCMaD94UCY5/qk3S40khch21qdN7tDOAG3nvZj9S0SKu XhQObotmKhwL9vJdrVlplUjktU3WGr7pAlM6z8LGVriY5y+kbtq1IKWJkOLIgmDx YmzSR8cS+3jQTOFOhfj8lsYgf/NmrQE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=WDI5X0zPnE09j+KEhEc9qtze7Jc90MLo7K8yjkX14 u8=; b=Ooo87tW94hGAVguQS8qGgFQpjSGGzaGOpO/7QQBcD+O4pFqUQTG78rNXg ofHYf4/URCCSA2zxEa1M+/ibqL8dZuydLI+cOF9kPyT2zoK8IQ6LlVUa+v750Fjk ZQNOpmx6dCDowjx4UIhMX0u1EprDCfqKl0L8ENG9E50KNNBRnvQFDux6s6p8OWpj nS4M+YNiTI0sUwYHjiNWsOY2JbbQnmucXWFZMupOgHH0GxKjNsauw0T3NAQi8ZDL qMxpuN7sMO9/jKxcU9ptJWgQ0sZmDp/ccrESzK3QjwQZtvmigapDrljfAHeC2XB0 nR+42Yg/hVNtxUnfk8qPFOKkJgGfA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeejgdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrg hrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucev lhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4D07FE49E2; Fri, 29 Mar 2019 10:16:40 -0400 (EDT) From: Thomas Monjalon To: Hajkowski Cc: dev@dpdk.org, david.hunt@intel.com Date: Fri, 29 Mar 2019 15:16:38 +0100 Message-ID: <1813744.7UKQrVtjkc@xps> In-Reply-To: <20190321105506.6656-1-marcinx.hajkowski@intel.com> References: <20190321105506.6656-1-marcinx.hajkowski@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v3 0/4] bidirect guest channel X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190329141638.ebB9Xznhipt82j_RfdyCRrxyCdeRFpX_qVI1v8TmvEo@z> 21/03/2019 11:55, Hajkowski: > From: Marcin Hajkowski > > Extend guest channel API to allow bidirectional > communication. Modify power manager host and guest > side to communicate in both directions. > > v3: > * fix global_fds[lcore_id] comparison to invalid value > * check 0 to verify if read function actually read some data > * define _NACK cmd instead of _NAK > * simplify rte_power_guest_channel_receive_msg func logic > > v2: > * send ack only if power operation return positive value > * log diffent error for unexpected incoming command and > error during ack/nak cmd sending Please use --in-reply-to to keep all versions in the same thread, thanks.