patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Stojaczyk, Dariusz" <dariusz.stojaczyk@intel.com>
Cc: dev@dpdk.org, "Wang, Xiao W" <xiao.w.wang@intel.com>,
	Alejandro Lucero <alejandro.lucero@netronome.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/2] eal/vfio: check if we already have the group fd open
Date: Mon, 29 Oct 2018 01:26:38 +0100	[thread overview]
Message-ID: <14140752.NalxdHykFh@xps> (raw)
In-Reply-To: <B7F2E978279D1D49A3034B7786DACF406F9C51C2@SHSMSX101.ccr.corp.intel.com>

25/09/2018 09:56, Wang, Xiao W:
> Hi,
> 
> > From: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>
> > 
> > Always attempt to find already opened fd for an iommu
> > group as subsequent attempts to open it will fail.
> > 
> > There's no public API to check if a group was already
> > bound and has a container, so rte_vfio_container_group_bind()
> > shouldn't fail in such case.
> > 
> > Fixes: ea2dc1066870 ("vfio: add multi container support")
> > Cc: xiao.w.wang@intel.com
> > 
> > Signed-off-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>
> 
> Acked-by: Xiao Wang <xiao.w.wang@intel.com>

+Cc: stable@dpdk.org

Series applied, thanks

  reply	other threads:[~2018-10-29  0:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:46 [dpdk-stable] " Darek Stojaczyk
2018-09-17 13:46 ` [dpdk-stable] [PATCH 2/2] eal/vfio: cleanup getting group fd Darek Stojaczyk
2018-09-26 12:34   ` Burakov, Anatoly
2018-09-25  7:56 ` [dpdk-stable] [PATCH 1/2] eal/vfio: check if we already have the group fd open Wang, Xiao W
2018-10-29  0:26   ` Thomas Monjalon [this message]
2018-09-26 12:35 ` Burakov, Anatoly

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=14140752.NalxdHykFh@xps \
    --to=thomas@monjalon.net \
    --cc=alejandro.lucero@netronome.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dariusz.stojaczyk@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=xiao.w.wang@intel.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).