DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vfio: failed to select IOMMU type
Date: Mon, 24 Apr 2017 09:09:03 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697822102A2@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <CAD+H992-EcByEEG9cTg2gCBH-2=uRnySdANd=YV2eTMt4h4uwg@mail.gmail.com>

Hi Alejandro,

> I have tested this approach and it works for the single device per group case, which is the one I can test by now. But I'm not sure I understood this comment about using a old kernel for testing the multiple devices per group case. Can you confirm if I understood this correctly? If I use an old kernel, devices like VFs are created in the same IOMMU group?

I cannot confirm this for every use case, but I've done some recent testing with VFIO on an old kernel for an unrelated patch, and I noticed that if I used kernel 3.6, all my physical ports were assigned the same IOMMU group (as opposed to different ones with a more recent kernel). So I think it's a safe bet to at least try and test this on your side :) 

Thanks,
Anatoly


      reply	other threads:[~2017-04-24  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 10:46 Andrew Rybchenko
2017-04-03 16:11 ` Burakov, Anatoly
2017-04-04 15:29   ` Andrew Rybchenko
2017-04-04 15:52     ` Burakov, Anatoly
2017-04-04 16:10       ` Andrew Rybchenko
2017-04-04 16:20         ` Burakov, Anatoly
2017-04-05  7:15           ` Alejandro Lucero
2017-04-05  7:12       ` Alejandro Lucero
2017-04-06  9:10         ` Burakov, Anatoly
2017-04-18 11:22           ` Alejandro Lucero
2017-04-24  9:09             ` Burakov, Anatoly [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=C6ECDF3AB251BE4894318F4E45123697822102A2@IRSMSX109.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=arybchenko@solarflare.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).