From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "He, Shaopeng" <shaopeng.he@intel.com>
Subject: Re: [dpdk-dev] [PATCH] fm10k: support XEN domain0
Date: Fri, 5 Jun 2015 03:17:53 +0000 [thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC0575FDE4@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1431680162-13704-1-git-send-email-shaopeng.he@intel.com>
Acked-by: Jijiang Liu <Jijiang.liu@intel.com>
I think this patch could be merged before Stephen's following patch[1] is merged, then Stephen should rework the patch[1].
Thanks.
[1]http://dpdk.org/ml/archives/dev/2015-March/014992.html
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shaopeng He
> Sent: Friday, May 15, 2015 4:56 PM
> To: dev@dpdk.org
> Cc: He, Shaopeng
> Subject: [dpdk-dev] [PATCH] fm10k: support XEN domain0
>
> fm10k was failing to run in XEN domain0, as the physical memory for DMA
> should be allocated and translated in a different way for XEN domain0. So
> rte_memzone_reserve_bounded() should be used for DMA memory
> allocation, and rte_mem_phy2mch() should be used for DMA memory
> address translation to support running fm10k PMD in XEN domain0.
>
> Signed-off-by: Shaopeng He <shaopeng.he@intel.com>
> ---
> lib/librte_pmd_fm10k/fm10k_ethdev.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/lib/librte_pmd_fm10k/fm10k_ethdev.c
> b/lib/librte_pmd_fm10k/fm10k_ethdev.c
> index 275c19c..c85c856 100644
> --- a/lib/librte_pmd_fm10k/fm10k_ethdev.c
> +++ b/lib/librte_pmd_fm10k/fm10k_ethdev.c
> @@ -1004,7 +1004,11 @@ fm10k_rx_queue_setup(struct rte_eth_dev *dev,
> uint16_t queue_id,
> return (-ENOMEM);
> }
> q->hw_ring = mz->addr;
> +#ifdef RTE_LIBRTE_XEN_DOM0
> + q->hw_ring_phys_addr = rte_mem_phy2mch(mz->memseg_id, mz-
> >phys_addr);
> +#else
> q->hw_ring_phys_addr = mz->phys_addr;
> +#endif
>
> dev->data->rx_queues[queue_id] = q;
> return 0;
> @@ -1150,7 +1154,11 @@ fm10k_tx_queue_setup(struct rte_eth_dev *dev,
> uint16_t queue_id,
> return (-ENOMEM);
> }
> q->hw_ring = mz->addr;
> +#ifdef RTE_LIBRTE_XEN_DOM0
> + q->hw_ring_phys_addr = rte_mem_phy2mch(mz->memseg_id, mz-
> >phys_addr);
> +#else
> q->hw_ring_phys_addr = mz->phys_addr;
> +#endif
>
> /*
> * allocate memory for the RS bit tracker. Enough slots to hold the
> --
> 1.9.3
next prev parent reply other threads:[~2015-06-05 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 8:56 Shaopeng He
2015-05-15 10:21 ` Thomas Monjalon
2015-05-15 23:57 ` Stephen Hemminger
2015-05-18 2:23 ` Liu, Jijiang
2015-06-02 3:27 ` He, Shaopeng
2015-06-05 3:17 ` Liu, Jijiang [this message]
2015-06-23 1:21 ` He, Shaopeng
2015-06-30 3:27 ` He, Shaopeng
2015-07-01 10:47 ` Thomas Monjalon
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=1ED644BD7E0A5F4091CF203DAFB8E4CC0575FDE4@SHSMSX101.ccr.corp.intel.com \
--to=jijiang.liu@intel.com \
--cc=dev@dpdk.org \
--cc=shaopeng.he@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).