DPDK patches and discussions
 help / color / mirror / Atom feed
From: Santosh Shukla <sshukla@mvista.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] vfio/noiommu: Don't use iommu_present() to track fake groups
Date: Wed, 27 Jan 2016 19:11:29 +0530	[thread overview]
Message-ID: <CAAyOgsZuH+oqedTnz8MrZT1HYZGBbRu-TvLcqP0_6Ui+dU8W9Q@mail.gmail.com> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E45123697820C5056@IRSMSX109.ger.corp.intel.com>

On Wed, Jan 27, 2016 at 6:51 PM, Burakov, Anatoly
<anatoly.burakov@intel.com> wrote:
> Hi Alex,
>
>> On 01/23/2016 04:23 AM, Alex Williamson wrote:
>> > Using iommu_present() to determine whether an IOMMU group is real or
>> > fake has some problems.  First, apparently Power systems don't
>> > register an IOMMU on the device bus, so the groups and containers get
>> > marked as noiommu and then won't bind to their actual IOMMU driver.
>> > Second, I expect we'll run into the same issue as we try to support
>> > vGPUs through vfio, since they're likely to emulate this behavior of
>> > creating an IOMMU group on a virtual device and then providing a vfio
>> > IOMMU backend tailored to the sort of isolation they provide, which
>> > won't necessarily be fully compatible with the IOMMU API.
>> >
>> > The solution here is to use the existing iommudata interface to IOMMU
>> > groups, which allows us to easily identify the fake groups we've
>> > created for noiommu purposes.  The iommudata we set is purely
>> > arbitrary since we're only comparing the address, so we use the
>> > address of the noiommu switch itself.
>> >
>> > Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> > Fixes: 03a76b60f8ba ("vfio: Include No-IOMMU mode")
>> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>>
>>
>>
>> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> Tested-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
> Tested bringing the NIC's up, encountered no issues. Curious if it also works for Santosh (CC'd) as he's one of the intended users of the No-IOMMU functionality, but otherwise seems to work.
>

Yes, Its works for virtio dpdk case too, Tested-by:

Thanks.
> Thanks,
> Anatoly

      reply	other threads:[~2016-01-27 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 17:23 Alex Williamson
2016-01-25  0:20 ` Alexey Kardashevskiy
2016-01-27 13:21   ` Burakov, Anatoly
2016-01-27 13:41     ` Santosh Shukla [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=CAAyOgsZuH+oqedTnz8MrZT1HYZGBbRu-TvLcqP0_6Ui+dU8W9Q@mail.gmail.com \
    --to=sshukla@mvista.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.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).