From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"JPF@zurich.ibm.com" <JPF@zurich.ibm.com>,
Gowrishankar Muthukrishnan <gowrishankar.m@in.ibm.com>
Subject: Re: [dpdk-dev] [PATCH dpdk 4/5] vfio: Do try setting IOMMU type if already set
Date: Wed, 26 Apr 2017 11:24:22 +0100 [thread overview]
Message-ID: <CAD+H993aNfm5Tw6tC=hoxCsiO_tadwjSveThzDb5501EV1id3w@mail.gmail.com> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E4512369782210A53@IRSMSX109.ger.corp.intel.com>
On Wed, Apr 26, 2017 at 9:58 AM, Burakov, Anatoly <anatoly.burakov@intel.com
> wrote:
> Hi Alejandro,
>
> > I was counting on first submitted patch being accepted.
>
> OK, that's on me then.
>
> > There is another thing to solve which is to unplug ports when there are
> more than one (already plugged) in an IOMMU group. I have a patch for this
> but I can not test it for that scenario, just for the "normal" one with one
> port/device per IOMMU group. > I'm working on having a way for testing the
> first case.
>
> Have you tried older kernel versions yet? Those seem to work for me.
>
>
I'm trying that one but run in some problems. Likely that is the quickest
way although I'm thinking on adding some option to the kernel for people
with such a hardware being able to test that option.
> > The only problem is after that, none else device hotplug can happen. I
> know that is not a good thing because it requires to restart the app, but
> better than breaking the app with a crash.
>
> Presumably, you're only talking about VFIO hotplug, and not hotplug in
> general? Is there anything that can be done to fix this issue in the long
> run?
>
>
Yes, just talking about VFIO. I think that patch I have should solve the
issue. It is just a matter of tracking how many devices are in use on a
vfio group, so just adding a new field to struct vfio_group and checking
number of devices when unplugging should be enough. Just when is the only
device plugged should close the vfio group.
> Thanks,
> Anatoly
>
>
next prev parent reply other threads:[~2017-04-26 10:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 7:23 [dpdk-dev] [PATCH dpdk 0/5] ppc64/spapr: Attempt to use on POWER8 Alexey Kardashevskiy
2017-04-20 7:23 ` [dpdk-dev] [PATCH dpdk 1/5] vfio/ppc64/spapr: Use correct structures for add/remove windows Alexey Kardashevskiy
2017-04-20 7:23 ` [dpdk-dev] [PATCH dpdk 2/5] pci: Initialize common rte driver pointer Alexey Kardashevskiy
2017-04-24 9:28 ` Burakov, Anatoly
2017-04-20 7:24 ` [dpdk-dev] [PATCH dpdk 3/5] RFC: bnx2x: Update firmware versions Alexey Kardashevskiy
2017-04-20 7:24 ` [dpdk-dev] [PATCH dpdk 4/5] vfio: Do try setting IOMMU type if already set Alexey Kardashevskiy
2017-04-20 19:31 ` gowrishankar muthukrishnan
2017-04-21 8:54 ` Andrew Rybchenko
2017-04-26 7:50 ` Alexey Kardashevskiy
2017-04-26 8:27 ` Burakov, Anatoly
2017-04-26 8:45 ` Alejandro Lucero
2017-04-26 8:58 ` Burakov, Anatoly
2017-04-26 10:24 ` Alejandro Lucero [this message]
2017-04-20 7:24 ` [dpdk-dev] [PATCH dpdk 5/5] RFC: vfio/ppc64/spapr: Use correct bus addresses for DMA map Alexey Kardashevskiy
2017-04-20 9:04 ` Jonas Pfefferle1
2017-04-20 13:25 ` Alexey Kardashevskiy
2017-04-20 14:22 ` Alexey Kardashevskiy
2017-04-20 15:15 ` Jonas Pfefferle1
2017-04-20 22:01 ` Alexey Kardashevskiy
2017-04-20 19:16 ` gowrishankar muthukrishnan
2017-04-21 3:42 ` Alexey Kardashevskiy
2017-04-21 8:43 ` Alexey Kardashevskiy
[not found] ` <OF6F33ED54.7950E1EF-ONC1258109.003295E3-C1258109.00333E2E@notes.na.collabserv.com>
2017-04-22 0:12 ` Alexey Kardashevskiy
2017-04-24 9:40 ` Burakov, Anatoly
2017-04-21 8:51 ` gowrishankar muthukrishnan
[not found] ` <OF45247CC5.192F9D29-ONC1258109.002D6497-C1258109.002F2868@notes.na.collabserv.com>
2017-04-21 8:59 ` Alexey Kardashevskiy
2017-04-22 21:11 ` [dpdk-dev] [PATCH dpdk 0/5] ppc64/spapr: Attempt to use on POWER8 Olga Shern
2017-04-23 13:35 ` Alexey Kardashevskiy
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+H993aNfm5Tw6tC=hoxCsiO_tadwjSveThzDb5501EV1id3w@mail.gmail.com' \
--to=alejandro.lucero@netronome.com \
--cc=JPF@zurich.ibm.com \
--cc=aik@ozlabs.ru \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@in.ibm.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).