Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753500AbcLBQCw (ORCPT ); Fri, 2 Dec 2016 11:02:52 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:39714 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750750AbcLBQCv (ORCPT ); Fri, 2 Dec 2016 11:02:51 -0500 Date: Fri, 2 Dec 2016 17:02:59 +0100 From: Greg KH To: KY Srinivasan Cc: "olaf@aepfle.de" , "jasowang@redhat.com" , Haiyang Zhang , "linux-kernel@vger.kernel.org" , "apw@canonical.com" , "devel@linuxdriverproject.org" , "leann.ogasawara@canonical.com" Subject: Re: [PATCH 02/15] hyperv: Add a function to detect hv_device Message-ID: <20161202160259.GA6050@kroah.com> References: <1480613287-7748-1-git-send-email-kys@exchange.microsoft.com> <1480613332-7788-1-git-send-email-kys@exchange.microsoft.com> <1480613332-7788-2-git-send-email-kys@exchange.microsoft.com> <20161201203547.GB1602@kroah.com> <20161202064805.GA19267@kroah.com> <20161202073614.GA21628@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1526 Lines: 38 On Fri, Dec 02, 2016 at 03:38:51PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:gregkh@linuxfoundation.org] > > Sent: Thursday, December 1, 2016 11:36 PM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org; > > olaf@aepfle.de; apw@canonical.com; vkuznets@redhat.com; > > jasowang@redhat.com; leann.ogasawara@canonical.com; Haiyang Zhang > > > > 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... > Greg, > > This is even worse. On Linux, VF drivers are hypervisor agnostic > and I want to keep it that way. Ok, I really don't know what to suggest, other than this is probably not the way to do this as no other bus has to. As I don't see the code that actually uses this anywhere, it's really impossible to have this conversation at all :( greg k-h