[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161202073614.GA21628@kroah.com>
Date: Fri, 2 Dec 2016 08:36:14 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: KY Srinivasan <kys@...rosoft.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: Re: [PATCH 02/15] hyperv: Add a function to detect hv_device
On Fri, Dec 02, 2016 at 07:14:03AM +0000, KY Srinivasan wrote:
> > In other words, why do you need this and PCI or USB doesn't? Why is
> > hyperv "special"?
>
> On Hyper-V, each VF interface (SR-IOV interface)
> is paired with an instance of the
> synthetic interface that is managed by netvsc.
> When the VF interface comes up, we
> need to associate the VF instance with
> the corresponding netvsc instance. To do this
> without modifying the VF drivers, netvsc registers
> for netdev events.
Why not modify the VF drivers? You have the full source to them...
Powered by blists - more mailing lists