DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: enable vfio independent of PCI bus
Date: Tue, 24 Oct 2017 00:32:46 +0200	[thread overview]
Message-ID: <1599654.GbReubtbfy@xps> (raw)
In-Reply-To: <6ef50a0e-02d4-7460-d5ee-5564c64b9396@intel.com>

23/10/2017 13:47, Burakov, Anatoly:
> On 11-Oct-17 7:42 AM, Hemant Agrawal wrote:
> > VFIO may be used by buses other than PCI. This patch enables
> > the VFIO on the basis of vfio root presence.
> > 
> > Since vfio_enable should be called only once, pci_vfio_enable
> > is also removed.
> > 
> > A debug print is added in case vfio_pci module is not present.
> > 
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks

      reply	other threads:[~2017-10-23 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 11:48 [dpdk-dev] [PATCH] eal: fslmc bus need vfio enabled for non PCI case as well Hemant Agrawal
2017-10-05 23:41 ` Thomas Monjalon
2017-10-06 16:22   ` Hemant Agrawal
2017-10-06 17:08     ` Thomas Monjalon
2017-10-07 11:22       ` Hemant Agrawal
2017-10-07 11:20 ` [dpdk-dev] [PATCH v2] eal: enable vfio independent of no PCI flag Hemant Agrawal
2017-10-07 11:37   ` Thomas Monjalon
2017-10-10 13:46     ` Hemant Agrawal
2017-10-10 16:27       ` Thomas Monjalon
2017-10-11  6:42   ` [dpdk-dev] [PATCH v3] eal: enable vfio independent of PCI bus Hemant Agrawal
2017-10-23  6:33     ` [dpdk-dev] FW: " Hemant Agrawal
2017-10-23 11:00       ` Burakov, Anatoly
2017-10-23 11:47     ` [dpdk-dev] " Burakov, Anatoly
2017-10-23 22:32       ` 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=1599654.GbReubtbfy@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).