From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id BD7474C8D for ; Tue, 15 Jan 2019 00:15:53 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4921F2891E; Mon, 14 Jan 2019 18:15:53 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 14 Jan 2019 18:15:53 -0500 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=1HntSDJpaQbwscjaTcElVL4h0bGaoFJzNwHYtrcr43c=; b=OPn6Mhwvcrjb HyOoXFLYny5EIA7h7lqZGvURX0Gtv+4pEKv/CgPZ98gboi2vxwYcoAKE9YW1S+P3 iigWowU7eAjjeIhNaljxz7xfiBH0QqxPiQLzhwvaSl2egXUeJvjZQM4fWy+SQn55 uOBu3/iz2mUGWU96mSrsP7i8O8RX2NA= 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=fm1; bh=1HntSDJpaQbwscjaTcElVL4h0bGaoFJzNwHYtrcr4 3c=; b=IEYNJUSn/YolhKlxbj8Zv5wdj6zSZU5zrLd5RKtfL1vVDOOWM269HhhUH AQASH6fwVM23Ss/slu/5JbVwzdVzs+1NBoE4AULBxB5gAAh/hNH3TZN72JQze9HP /udcQdSv3FuTnKL4LZIbSDxBE03LTSxC2DEVpw9buN4JObC09R320K3YhsPfBzqB 2TCpdFwikwO5II/W0Vz1IKjhrmWvRPXYnaL5Umg3RE+C8myAST4Mybc8sa4FIwnT hkjejf183ZZGYi9CPmOgAXNFddLcuf5e958ZN5GMTT6QS86UW0qVvlGufoLAr9GD mX7htQCIJs6U6fY2I+Fcd1p2KdBkA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgedvgddtiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 2E5E7E40E1; Mon, 14 Jan 2019 18:15:52 -0500 (EST) From: Thomas Monjalon To: "Hunt, David" Cc: dev@dpdk.org, "Yao, Lei A" Date: Tue, 15 Jan 2019 00:15:51 +0100 Message-ID: <3764870.CNDs0HdWOl@xps> In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D95496070BB@shsmsx102.ccr.corp.intel.com> References: <20190107113920.37748-1-david.hunt@intel.com> <450fa9eb-fedd-969a-fbb4-c98472cdb1f5@intel.com> <2DBBFF226F7CF64BAFCA79B681719D95496070BB@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] examples/power: fix wrong core_id with JSON cmds 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: Mon, 14 Jan 2019 23:15:53 -0000 > > >> This patch fixes a bug introduced in the 64-core limtation > > >> enhancement where the core_id is inadvertently converted from > > >> virtual to physical even though it may already be a physical > > >> core_id. > > >> > > >> We should be using the core_type field, and only converting via > > >> hypervisor when core_type is set to CORE_TYPE_VIRTUAL > > >> > > >> Fixes: 5776b7a371d1 ("examples/power: allow VM to use lcores over 63") > > >> > > >> Signed-off-by: David Hunt > Reviewed-by: Lei Yao > Tested-by: Lei Yao Applied, thanks