From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] vfio: add hotplug support
Date: Wed, 29 Mar 2017 10:32:07 +0100 [thread overview]
Message-ID: <CAD+H990-VO4ye7ksoveY=p4a7FeVWaiFDixOq+D20AtH0wru-A@mail.gmail.com> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E451236978220B80B@IRSMSX109.ger.corp.intel.com>
On Wed, Mar 29, 2017 at 9:57 AM, Burakov, Anatoly <anatoly.burakov@intel.com
> wrote:
> Hi Alejandro,
>
> > From: Alejandro Lucero [mailto:alejandro.lucero@netronome.com]
> > Sent: Monday, March 27, 2017 11:56 AM
> > To: Burakov, Anatoly <anatoly.burakov@intel.com>
> > Cc: dev@dpdk.org
> > Subject: [PATCH v2] vfio: add hotplug support
> >
> > Current device hotplug is just supported by UIO managed devices.
> > This patch adds same functionality with VFIO.
> >
> > It has been validated through tests using IOMMU and also with VFIO and
> no-
> > iommu mode.
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> > ---
> > app/Makefile | 1 +
> > doc/guides/prog_guide/port_hotplug_framework.rst | 2 +-
> > doc/guides/rel_notes/release_17_05.rst | 4 +
> > lib/librte_eal/common/eal_common_pci.c | 2 +-
> > lib/librte_eal/linuxapp/eal/eal_pci.c | 5 +-
> > lib/librte_eal/linuxapp/eal/eal_pci_init.h | 3 +-
> > lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 85 +++++++++-
> > lib/librte_eal/linuxapp/eal/eal_vfio.c | 197
> ++++++++++++++++++-----
> > lib/librte_eal/linuxapp/eal/eal_vfio.h | 10 +-
> > lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c | 23 ++-
> > lib/librte_ether/rte_ethdev.c | 2 +-
> > 11 files changed, 276 insertions(+), 58 deletions(-)
> >
> > diff --git a/app/Makefile b/app/Makefile index 4b3a448..fe3fed1 100644
> > --- a/app/Makefile
> > +++ b/app/Makefile
> > @@ -35,5 +35,6 @@ DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd
> > DIRS-$(CONFIG_RTE_APP_CRYPTO_PERF) += test-crypto-perf
> > DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += proc_info
> > DIRS-$(CONFIG_RTE_LIBRTE_PDUMP) += pdump
> > +DIRS-y += multivf
>
> I think an unrelated change has snuck into the patch?
>
Oops.
I would fix this asap and send another patch version.
Thanks
prev parent reply other threads:[~2017-03-29 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 10:55 Alejandro Lucero
2017-03-29 8:57 ` Burakov, Anatoly
2017-03-29 9:32 ` Alejandro Lucero [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='CAD+H990-VO4ye7ksoveY=p4a7FeVWaiFDixOq+D20AtH0wru-A@mail.gmail.com' \
--to=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.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).