DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/2] vfio: build cleanups
Date: Thu,  9 Jul 2015 16:26:25 -0700	[thread overview]
Message-ID: <1436484387-29273-1-git-send-email-stephen@networkplumber.org> (raw)

In our environment we build on old system (2.6.32) but want
to have VFIO enabled. This was the best solution after many
different experiments.  There was an earlier discussion and
the solution proposed then was significantly different.

Stephen Hemminger (2):
  vfio: fix build if build envrionment is on old kernel
  vfio: don't build unnecessary files

 lib/librte_eal/linuxapp/eal/Makefile               |   4 +-
 lib/librte_eal/linuxapp/eal/compat_vfio.h          | 181 +++++++++++++++++++++
 lib/librte_eal/linuxapp/eal/eal_pci_vfio.c         |   3 -
 lib/librte_eal/linuxapp/eal/eal_pci_vfio_mp_sync.c |   3 -
 lib/librte_eal/linuxapp/eal/eal_vfio.h             |  13 +-
 5 files changed, 190 insertions(+), 14 deletions(-)
 create mode 100644 lib/librte_eal/linuxapp/eal/compat_vfio.h

-- 
2.1.4

             reply	other threads:[~2015-07-09 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 23:26 Stephen Hemminger [this message]
2015-07-09 23:26 ` [dpdk-dev] [PATCH v2 1/2] vfio: fix build if build envrionment is on old kernel Stephen Hemminger
2015-07-09 23:43   ` Thomas Monjalon
2015-07-10 17:29     ` Stephen Hemminger
2015-07-10 20:19       ` Thomas Monjalon
2015-07-10 20:44         ` Stephen Hemminger
2015-07-10 21:10           ` Thomas Monjalon
2015-07-10 10:13   ` Burakov, Anatoly
2015-07-10 15:44     ` Stephen Hemminger
2015-07-09 23:26 ` [dpdk-dev] [PATCH v2 2/2] vfio: don't build unnecessary files Stephen Hemminger

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=1436484387-29273-1-git-send-email-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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).