All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: echaudron@redhat.com
Cc: Eelco Chaudron <echaudro@redhat.com>, dev <dev@dpdk.org>,
	mukawa@igel.co.jp
Subject: Re: Hotplug support for VFIO
Date: Wed, 8 Feb 2017 15:43:13 +0000	[thread overview]
Message-ID: <CAD+H9907pxGvbHFmaP1xaaBNe+yuwCKhug8adL2oExPa2J8nwA@mail.gmail.com> (raw)
In-Reply-To: <ce3c365e-9211-bc36-8430-b57847b75be1@redhat.com>

Hi Eelco,

On Wed, Feb 8, 2017 at 9:41 AM, Eelco Chaudron <echaudron@redhat.com> wrote:

> Hi Anatoly,
>
> This will be great... If you want I can do some testing on (early) patches
> if required.
>
> Also do you know why it is currently not supported, i.e. what are the
> limitations?
>
> Thanks,
>

I assume your reply was to my previous email and not to Anatoly's one. My
apologies if this assumption is wrong.
By the way, you did not reply to the list, but I'm doing to do so because
this could be interesting to other people. Also, I'm CCing hotplug UIO
developer, Tetsuya Mukawa, since there is no a specific maintainer for this
functionality.

I think the main problem for supporting VFIO hotplug is to deal with what
VFIO does, this is IOMMU mappings.
There is no code for doing so, and although the implementation would use
most of the code already there for UIO hotplug, which is basically related
to unmapping PCI resources, and the interrupt part will be likely quite
similar, the IOMMU unmapping requires more work.

I dare to say this is the main reason for not having VFIO hotplug support
right now. Maybe Tetsuya can confirm this or give us other reasons.


>
> Eelco
>
>
>
> On 07/02/17 10:29, Alejandro Lucero wrote:
>
> It seems none is working on this VFIO support.
>
> I will work on this if there is no reply to this thread saying the
> opposite the next days.
>
> On Thu, Feb 2, 2017 at 12:58 PM, Eelco Chaudron <echaudron@redhat.com>
> wrote:
>
>> On 02/02/17 13:05, Burakov, Anatoly wrote:
>>
>>> Hi Eelco,
>>>
>>> Please forgive me my ignorance on this matter, but doesn't it work at
>>> the moment? I would assume that if regular PCI hotplug works (with
>>> igb_uio), then so would hotplug with VFIO, as it basically utilizes the
>>> same PCI infrastructure igb_uio does. That said, I'm not aware of any
>>> patches submitted that had to do with VFIO and hotplug, so I guess the
>>> answer is, not at the moment.
>>>
>>> Thanks,
>>> Anatoly
>>>
>> I was asking as the documentation explicitly mentions its not supported.
>> http://dpdk.org/doc/guides/prog_guide/port_hotplug_framework.html#hotplug
>>
>> - "To detach a port, the port should be backed by a device that igb_uio
>> manages. VFIO is not supported."
>>
>> I could not find any specific reason why it's not supported, so if some
>> one can explain this it would help also...
>>
>> Cheers,
>>
>> Eelco
>>
>>
>>
>
>

  parent reply	other threads:[~2017-02-08 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 11:23 Hotplug support for VFIO Eelco Chaudron
2017-02-02 12:05 ` Burakov, Anatoly
2017-02-02 12:58   ` Eelco Chaudron
2017-02-07  9:29     ` Alejandro Lucero
     [not found]       ` <ce3c365e-9211-bc36-8430-b57847b75be1@redhat.com>
2017-02-08 15:43         ` Alejandro Lucero [this message]
2017-02-08 15:48           ` Alejandro Lucero
2017-02-09  3:56             ` Tetsuya Mukawa
     [not found]             ` <CANbst6F=MvCF0-1d7Q+2CFw0=7YtQ11NV4YtgB26T8MXHfQLJA@mail.gmail.com>
2017-02-10 10:08               ` Alejandro Lucero

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+H9907pxGvbHFmaP1xaaBNe+yuwCKhug8adL2oExPa2J8nwA@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=echaudro@redhat.com \
    --cc=echaudron@redhat.com \
    --cc=mukawa@igel.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.