DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "echaudro@redhat.com" <echaudro@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Hotplug support for VFIO
Date: Thu, 2 Feb 2017 12:05:48 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697821E600C@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1eca3907-39e6-2b09-a8fc-fe894988cc79@redhat.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Eelco Chaudron
> Sent: Thursday, February 2, 2017 11:24 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Hotplug support for VFIO
> 
> Hi,
> 
> I was wondering if some one is working on VFIO hotplug support?
> 
> Cheers,
> 
> Eelco

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

  reply	other threads:[~2017-02-02 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 11:23 Eelco Chaudron
2017-02-02 12:05 ` Burakov, Anatoly [this message]
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
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=C6ECDF3AB251BE4894318F4E45123697821E600C@IRSMSX109.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=echaudro@redhat.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).