From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8FB12A0487 for ; Mon, 29 Jul 2019 15:13:28 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 486FB1BF95; Mon, 29 Jul 2019 15:13:28 +0200 (CEST) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id DB5FD1BF7E; Mon, 29 Jul 2019 15:13:21 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jul 2019 06:13:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,322,1559545200"; d="scan'208";a="162184065" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.92]) ([10.237.220.92]) by orsmga007.jf.intel.com with ESMTP; 29 Jul 2019 06:13:19 -0700 To: dev@dpdk.org Cc: Bruce Richardson , stable@dpdk.org References: <09c3f9d74e1e49aa5b3608d4bf4a773d086e83ff.1564398617.git.anatoly.burakov@intel.com> <3f4bf9cdf8b472e05e76274f6e8df5be936b01a9.1564398617.git.anatoly.burakov@intel.com> From: "Burakov, Anatoly" Message-ID: <45c91a5f-0e80-d60f-a789-bd9cf299a641@intel.com> Date: Mon, 29 Jul 2019 14:13:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <3f4bf9cdf8b472e05e76274f6e8df5be936b01a9.1564398617.git.anatoly.burakov@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 2/2] eal: use base address hint to reserve space for mem config X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On 29-Jul-19 12:18 PM, Anatoly Burakov wrote: > Currently, mem config will be mapped without using the virtual > area reservation infrastructure, which means it will be mapped > at an arbitrary location. This may cause failures to map the > shared config in secondary process due to things like PCI > whitelist arguments allocating memory in a space where the > primary has allocated the shared mem config. > > Fix this by using virtual area reservation to reserve space for > the mem config, thereby avoiding the problem and reserving the > shared config (hopefully) far away from any normal memory > allocations. > > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov > --- Apologies for multiple sends, the email appeared to not be getting through... -- Thanks, Anatoly