DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] building LIBRTE_PMD_XENVIRT in 32bit triggers some errors
Date: Wed, 9 Dec 2015 15:54:17 -0200	[thread overview]
Message-ID: <CAJSM8J0ax6ZQRKWJr8vaFZGWnB_FvQLHm3YMCxKnGmpC=qeOtw@mail.gmail.com> (raw)
In-Reply-To: <CAJSM8J3QgywrVNZ8avtwWGa_i_JAjViLksgE477=pGoaDhz2Qw@mail.gmail.com>

On 4 December 2015 at 21:56, Martinx - ジェームズ <thiagocmartinsc@gmail.com> wrote:
>
> On 2 December 2015 at 12:05, Christian Ehrhardt
> <christian.ehrhardt@canonical.com> wrote:
> > Hi,
> > just FYI - building LIBRTE_PMD_XENVIRT in 32bit triggers some errors.
> >
> > I don't know if that part of the tree is actively maintained - It is
> > default off, in the config template config/common_linuxapp.
> >
> > I'm not even entirely sure if  LIBRTE_PMD_XENVIRT is still required.
> > I guess in the Dom0 you can go with uio-pci-generic these days, not
> > sure about para-virtual guests.
> >
> > Anyway I thought it might be worth to at least report.
> >
> > == Build drivers/net/xenvirt
> > gcc -Wp,-MD,./.rte_eth_xenvirt.o.d.tmp -m32 -pthread -fPIC
> > -march=native -DRTE_MACHINE_CPUFLAG_SSE -DRTE_MACHINE_CPUFLAG_SSE2
> > -DRTE_MACHINE_CPUFLAG_SSE3 -DRTE_MACHINE_CPUFLAG_SSSE3
> > -DRTE_MACHINE_CPUFLAG_SSE4_1 -DRTE_MACHINE_CPUFLAG_SSE4_2
> > -DRTE_MACHINE_CPUFLAG_AES -DRTE_MACHINE_CPUFLAG_PCLMULQDQ
> > -DRTE_MACHINE_CPUFLAG_AVX
> > -DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2,RTE_CPUFLAG_SSE3,RTE_CPUFLAG_SSSE3,RTE_CPUFLAG_SSE4_1,RTE_CPUFLAG_SSE4_2,RTE_CPUFLAG_AES,RTE_CPUFLAG_PCLMULQDQ,RTE_CPUFLAG_AVX
> >  -I/home/ubuntu/dpdk-2.2.0-rc2/build/include -include
> > /home/ubuntu/dpdk-2.2.0-rc2/build/include/rte_config.h -O3 -W -Wall
> > -Werror -Wstrict-prototypes -Wmissing-prototypes
> > -Wmissing-declarations -Wold-style-definition -Wpointer-arith
> > -Wcast-align -Wnested-externs -Wcast-qual -Wformat-nonliteral
> > -Wformat-security -Wundef -Wwrite-strings   -o rte_eth_xenvirt.o -c
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/rte_eth_xenvirt.c
> > In file included from
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/rte_eth_xenvirt.c:61:0:
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/virtqueue.h: In
> > function ‘virtqueue_enqueue_recv_refill’:
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/virtqueue.h:201:15:
> > error: cast from pointer to integer of different size
> > [-Werror=pointer-to-int-cast]
> >    (uint64_t) ((uint64_t)cookie->buf_addr + RTE_PKTMBUF_HEADROOM -
> > sizeof(struct virtio_net_hdr));
> >                ^
> > In file included from
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/rte_eth_xenvirt.c:51:0:
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/virtqueue.h: In
> > function ‘virtqueue_enqueue_xmit’:
> > /home/ubuntu/dpdk-2.2.0-rc2/build/include/rte_mbuf.h:1617:3: error:
> > cast from pointer to integer of different size
> > [-Werror=pointer-to-int-cast]
> >   ((t)((char *)(m)->buf_addr + (m)->data_off + (o)))
> >    ^
> > /home/ubuntu/dpdk-2.2.0-rc2/build/include/rte_mbuf.h:1631:32: note: in
> > expansion of macro ‘rte_pktmbuf_mtod_offset’
> >  #define rte_pktmbuf_mtod(m, t) rte_pktmbuf_mtod_offset(m, t, 0)
> >                                 ^
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/virtqueue.h:58:2:
> > note: in expansion of macro ‘rte_pktmbuf_mtod’
> >   rte_pktmbuf_mtod(mb, uint64_t)
> >   ^
> > /home/ubuntu/dpdk-2.2.0-rc2/drivers/net/xenvirt/virtqueue.h:241:24:
> > note: in expansion of macro ‘RTE_MBUF_DATA_DMA_ADDR’
> >   start_dp[idx].addr  = RTE_MBUF_DATA_DMA_ADDR(cookie);
> >                         ^
> > cc1: all warnings being treated as errors
> > /home/ubuntu/dpdk-2.2.0-rc2/mk/internal/rte.compile-pre.mk:126: recipe
> > for target 'rte_eth_xenvirt.o' failed
> > make[4]: *** [rte_eth_xenvirt.o] Error 1
> > /home/ubuntu/dpdk-2.2.0-rc2/mk/rte.subdir.mk:61: recipe for target
> > 'xenvirt' failed
> > make[3]: *** [xenvirt] Error 2
> > /home/ubuntu/dpdk-2.2.0-rc2/mk/rte.subdir.mk:61: recipe for target 'net' failed
> > make[2]: *** [net] Error 2
> > /home/ubuntu/dpdk-2.2.0-rc2/mk/rte.sdkbuild.mk:93: recipe for target
> > 'drivers' failed
> > make[1]: *** [drivers] Error 2
> > /home/ubuntu/dpdk-2.2.0-rc2/mk/rte.sdkroot.mk:124: recipe for target
> > 'all' failed
> > make: *** [all] Error 2
> >
> > Christian Ehrhardt
> > Software Engineer, Ubuntu Server
> > Canonical Ltd
>
> Hey guys,
>
>  Is there an easy / fast fix available for this bug?
>
>  DPDK 2.2 with Xen on 32-bit is broken now...
>
>  If not, there will be no way to enable Xen for next Ubuntu LTS, which
> is very sad...
>
>  I have a great Xen project planned for Ubuntu 16.04 + DPDK + Xen with
> DPDK Apps running on PV domUs!
>
> Thanks!
> Thiago

Hey guys,

 Sorry to insist on this subject but, the time for releasing DPDK 2.2
is near and DPDK build with Xen 32-bit is broken.

 If DPDK doesn't fix this, there will be no way to enable XenVirt
support for next Ubuntu LTS 16.04, which is a shame...

 I'm planning to use DPDK on Xen domUs (PVM, HVM, XenServer and on
Amazon EC2) powered exclusively by a supported version of Ubuntu but,
it is broken now...

 So, please, can someone take a look into this?    :-P

 Thanks in advance!

Cheers!
Thiago

  reply	other threads:[~2015-12-09 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 14:05 Christian Ehrhardt
2015-12-04 23:56 ` Martinx - ジェームズ
2015-12-09 17:54   ` Martinx - ジェームズ [this message]
2015-12-09 20:05     ` Thomas Monjalon
2015-12-09 22:48       ` Martinx - ジェームズ
2015-12-10  4:45         ` Xie, Huawei
2015-12-10  8:51           ` Thomas Monjalon
2015-12-21 18:03           ` Martinx - ジェームズ
2015-12-22  2:51             ` Xie, Huawei

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='CAJSM8J0ax6ZQRKWJr8vaFZGWnB_FvQLHm3YMCxKnGmpC=qeOtw@mail.gmail.com' \
    --to=thiagocmartinsc@gmail.com \
    --cc=dev@dpdk.org \
    /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).