From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal/ppc: revert fix mmap for memory initialization Date: Tue, 07 Nov 2017 00:30:51 +0100 Message-ID: <2195471.a96TPSDOjF@xps> References: <1509631099-31832-1-git-send-email-jpf@zurich.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, anatoly.burakov@intel.com, chaozhu@linux.vnet.ibm.com To: Jonas Pfefferle Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 25F521B32F for ; Tue, 7 Nov 2017 00:30:53 +0100 (CET) In-Reply-To: <1509631099-31832-1-git-send-email-jpf@zurich.ibm.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 02/11/2017 14:58, Jonas Pfefferle: > This reverts commit 284ae3e9ff9a92575c28c858efd2c85c8de6d440 > ("eal/ppc: fix mmap for memory initialization").The logic if the > address hint is respected on mmap is no different on POWER than > on x86 however the address layout of userspace applications might > be slightly different i.e. you might need to use a different > virt-baseaddr. We now warn if the address hint is not respected > (fae209f) thus users can try different virtual address bases. It depends on a patch which is not applied yet.