DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix KNI compiling issue on IBM Power
Date: Fri, 05 Dec 2014 15:52:36 +0100	[thread overview]
Message-ID: <94521173.H6dyulnjbO@xps13> (raw)
In-Reply-To: <20141205144200.GC29245@hmsreliant.think-freely.org>

2014-12-05 09:42, Neil Horman:
> On Fri, Dec 05, 2014 at 02:10:27PM +0100, Thomas Monjalon wrote:
> > 2014-12-04 15:05, Neil Horman:
> > > On Thu, Dec 04, 2014 at 04:59:59PM +0100, Thomas Monjalon wrote:
> > > > I'm convinced we need to work on the build system but it's another discussion
> > > > for next weeks. Speaking about that, the AF_PACKET PMD cannot be enabled because
> > > > dependencies are not checked before building it.
> > > > 
> > > I'm fine with that.  If we're going to make the build system contain a depedency
> > > checking mechanism, we'll start dynamically enabling them when support is
> > > detected.  Until then I'm fine with it being an opt in operation, as you know at
> > > build time what you're minimum kernel support levels are.
> > > 
> > > Speaking of enabling however, be careful of a double standard here.  I know that
> > > igb_uio won't build on some kernels either (linvlle posted in the
> > > irc channel about it earlier), because we don't detect the presence of needed
> > > defines.  Yet IGB_UIO is still universally enabled...
> > 
> > I'm really surprised. Please post an email to report the problem.
> > To my knowledge, igb_uio build on every supported Linux distributions
> > (kernel >= 2.6.32).
> > 
> 
> From the IRC session:
> 
> linville   CC [M]
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
> linville
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:
> In function ‘store_max_vfs’:
> linville
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:86:2:
> error: implicit declaration of function ‘strict_strtoul’
> [-Werror=implicit-function-declaration]
> linville   if (0 != strict_strtoul(buf, 0, &max_vfs))
> linville   ^

Yes, this issue is being fixed. Jincheng Miao should send a v3:
	http://dpdk.org/ml/archives/dev/2014-December/009182.html

> linville
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:
> In function ‘igbuio_dom0_mmap_phys’:
> linville
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:290:30:
> error: ‘_PAGE_IOMAP’ undeclared (first use in this function)
> linville   vma->vm_page_prot.pgprot |= _PAGE_IOMAP;
> linville                               ^

Xen is disabled by default. So this issue hasn't been raised yet.
Fixes are welcome.

> linville
> /home/linville/git/dpdk/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:290:30:
> note: each undeclared identifier is reported only once for each function it
> appears in
> linville cc1: all warnings being treated as errors
> linville does igb_uio only work with certain old kernels?
> linville I'm running 3.18-rc7

There are some bugs.
Thanks for reporting (it would more visible in another thread).

-- 
Thomas

      reply	other threads:[~2014-12-05 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 10:14 [dpdk-dev] [PATCH] Fix KNI compiling " Chao Zhu
2014-12-04 10:14 ` [dpdk-dev] [PATCH] Fix KNI compiling issue " Chao Zhu
2014-12-04 11:59   ` Thomas Monjalon
2014-12-04 13:29     ` Neil Horman
2014-12-04 13:47       ` Thomas Monjalon
2014-12-04 15:32         ` Neil Horman
2014-12-04 15:59           ` Thomas Monjalon
2014-12-04 20:05             ` Neil Horman
2014-12-05  9:11               ` Chao Zhu
2014-12-05 13:10               ` Thomas Monjalon
2014-12-05 14:42                 ` Neil Horman
2014-12-05 14:52                   ` 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=94521173.H6dyulnjbO@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).