From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, huilongx.xu@intel.com, waterman.cao@intel.com,
yuanhan.liu@intel.com, weichunx.chen@intel.com,
yu.y.liu@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/4] fix mempool creation with Xen Dom0
Date: Mon, 11 Jul 2016 19:09:44 +0200 [thread overview]
Message-ID: <5170616.VubuxP6OQF@xps13> (raw)
In-Reply-To: <1468232428-24088-1-git-send-email-olivier.matz@6wind.com>
2016-07-11 12:20, Olivier Matz:
> Since the recent mempool rework [1], Xen Dom0 is broken.
> This series aims at fixing it. I think it should be integrated
> in 16.07.
>
> As I don't have a full testing platform, any help in validating
> this patchset would be appreciated.
>
> [1] http://www.dpdk.org/ml/archives/dev/2016-May/039229.html
>
> Olivier Matz (4):
> eal: fix typo in Xen Dom0 specific code
> mbuf: set errno on pool creation error
> eal: fix retrieval of phys address with Xen Dom0
> mempool: fix creation with Xen Dom0
Applied with an additional fix:
xen: fix build as shared library
When building as shared library, the compiler complains for
undefined reference to `rte_xen_mem_phy2mch'
The symbol rte_xen_mem_phy2mch was introduced in DPDK 2.2
and has been called in mempool recently via rte_mem_phy2mch.
Fixes: c042ba20674a ("mempool: rework support of Xen dom0")
next prev parent reply other threads:[~2016-07-11 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 10:20 Olivier Matz
2016-07-11 10:20 ` [dpdk-dev] [PATCH 1/4] eal: fix typo in Xen Dom0 specific code Olivier Matz
2016-07-11 10:20 ` [dpdk-dev] [PATCH 2/4] mbuf: set errno on pool creation error Olivier Matz
2016-07-11 10:20 ` [dpdk-dev] [PATCH 3/4] eal: fix retrieval of phys address with Xen Dom0 Olivier Matz
2016-07-11 10:20 ` [dpdk-dev] [PATCH 4/4] mempool: fix creation " Olivier Matz
2016-07-11 16:23 ` [dpdk-dev] [PATCH 0/4] fix mempool " Olivier Matz
2016-07-11 17:09 ` Thomas Monjalon [this message]
2016-07-12 0:31 ` Chen, WeichunX
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=5170616.VubuxP6OQF@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=huilongx.xu@intel.com \
--cc=olivier.matz@6wind.com \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yu.y.liu@intel.com \
--cc=yuanhan.liu@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).