From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
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>
Subject: Re: [dpdk-dev] 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 [thread overview]
Message-ID: <1536495.S7tBJyRKdq@xps13> (raw)
In-Reply-To: <3d95435f-b253-7291-d2fd-24cba2a66ea0@intel.com>
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.
prev parent reply other threads:[~2016-07-18 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 9:22 Xu, HuilongX
2016-07-12 11:30 ` Olivier MATZ
2016-07-18 11:33 ` Sergio Gonzalez Monroy
2016-07-18 11:49 ` Olivier Matz
2016-07-18 13:15 ` Sergio Gonzalez Monroy
2016-07-18 13:34 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1536495.S7tBJyRKdq@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=huilongx.xu@intel.com \
--cc=olivier.matz@6wind.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).