From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: mutli process C/S model example init failed on xen
	dom0 with dpdk-16.07 rc2 package
Date: Mon, 18 Jul 2016 15:34:58 +0200
Message-ID: <1536495.S7tBJyRKdq@xps13>
References: <DF2A19295B96364286FEB7F3DDA27A4637B879F4@SHSMSX101.ccr.corp.intel.com>
 <0f4d2722-a9ed-1203-29df-46ad8a169cd7@6wind.com>
 <3d95435f-b253-7291-d2fd-24cba2a66ea0@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Olivier Matz <olivier.matz@6wind.com>, "Xu,
 HuilongX" <huilongx.xu@intel.com>, dev@dpdk.org, "Cao,
 Waterman" <waterman.cao@intel.com>, "Chen, WeichunX" <weichunx.chen@intel.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43])
 by dpdk.org (Postfix) with ESMTP id 51A36378B
 for <dev@dpdk.org>; Mon, 18 Jul 2016 15:35:00 +0200 (CEST)
Received: by mail-wm0-f43.google.com with SMTP id o80so117189856wme.1
 for <dev@dpdk.org>; Mon, 18 Jul 2016 06:35:00 -0700 (PDT)
In-Reply-To: <3d95435f-b253-7291-d2fd-24cba2a66ea0@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-07-18 14:15, Sergio Gonzalez Monroy:
> On 18/07/2016 12:49, Olivier Matz wrote:
> > On 07/18/2016 01:33 PM, Sergio Gonzalez Monroy wrote:
> >> On 12/07/2016 12:30, Olivier MATZ wrote:
> >>> I think we cannot expect that memory is initialized at 0 when using
> >>> Xen dom0. If I add the following (dirty) patch, I don't see a crash
> >>> anymore:
> >> I don't have a Xen system available right now, but I'm not sure I follow
> >> here.
> >> Are you saying that when we allocate pages/hugepages from Xen they are
> >> not zeroed?
> > I did not check it, but from the tests I've done, I suppose they're not.
> 
> If that is the case then I would suggest to zero all memory on EAL init 
> (only for Xen) so
> all memory is zeroed after init for both Linux and Xen.
> 
> What do you think about that?

It is an idea.
It is probable that you won't have any answer as the Xen support is
unmaintained:
	http://dpdk.org/ml/archives/dev/2016-July/043875.html
Feel free to make a patch to try fixing it or we can remove this
whole dead code.