From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932362AbcLIVpp (ORCPT ); Fri, 9 Dec 2016 16:45:45 -0500 Received: from mail-by2nam01on0092.outbound.protection.outlook.com ([104.47.34.92]:2561 "EHLO NAM01-BY2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932221AbcLIVpm (ORCPT ); Fri, 9 Dec 2016 16:45:42 -0500 From: Haiyang Zhang To: Stephen Hemminger CC: Greg KH , KY Srinivasan , "olaf@aepfle.de" , "linux-kernel@vger.kernel.org" , "bjorn.helgaas@gmail.com" , "apw@canonical.com" , "devel@linuxdriverproject.org" , "leann.ogasawara@canonical.com" , "jasowang@redhat.com" Subject: RE: [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers Thread-Topic: [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers Thread-Index: AQHSUR21+bJgO3U+U0emkkp2CWFPCaD+NO0AgACI2oCAAHx4AIAAtV0AgAAbvVCAAAhUgIAAENNg Date: Fri, 9 Dec 2016 21:31:25 +0000 Message-ID: References: <1481185988-30383-1-git-send-email-kys@exchange.microsoft.com> <1481186023-30429-1-git-send-email-kys@exchange.microsoft.com> <1481186023-30429-3-git-send-email-kys@exchange.microsoft.com> <20161208155604.GA4601@kroah.com> <20161209073122.GB1513@kroah.com> <20161209102030.1f550c5a@xeon-e3> <20161209122935.2bd0779e@xeon-e3> In-Reply-To: <20161209122935.2bd0779e@xeon-e3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=haiyangz@microsoft.com; x-originating-ip: [72.74.33.140] x-ms-office365-filtering-correlation-id: 1d5b98f2-f9b0-470e-17c3-08d4207abac2 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:CY4PR03MB2485; x-microsoft-exchange-diagnostics: 1;CY4PR03MB2485;7:m8yGjjJRX53ENea6IVNegwMQapAuctwYuploL08+EETko9cT2xYIweIolDkCv2hITnY6VKHmJoaGhDzyEXyFTgOArrBJfu4TSecrbGGxeSCk8f8pmlHMEtFO7KSvbbt9rLmHl1K3iaPpy5RIa/sNFayYCM1QgdbiXvawi6ud6cGiI8hM2iiL+yy7Nq6fjidXYJqAZiYc4nfWfWWxpZPae5tFFbHbRhFXqU7fIscZnglVacWTvyr8uHmDc/Ch4N+JsNqnwlnmwwSEPbmMnE/4ocf0NSb9vjGSOe+QFOlhLPKh9fb9Z8+EigcIY+PvBJkEwvo5nh35Y69v/n+/aA0DeNUzTjRO5tZz/sWa3eFteXrraSJ2rqavktg7BB3deSg4UusnmQ8r3am/0ZrG4yPp03LtumTtlA8IyZpj2xVAxwZ2xsg4X3KU1RY/HefA4jdVOHWl+8FSTnNpz+FNPybkLvPbuQ+dTcdMJXgNDuMvwQQ= x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(9452136761055)(140211028294663)(198206253151910); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(61425038)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123564025)(20161123562025)(20161123560025)(20161123555025)(6072148)(6047074);SRVR:CY4PR03MB2485;BCL:0;PCL:0;RULEID:;SRVR:CY4PR03MB2485; x-forefront-prvs: 015114592F x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(7916002)(39450400003)(39860400002)(39840400002)(39410400002)(39850400002)(40224003)(13464003)(199003)(377454003)(24454002)(189002)(7696004)(2950100002)(93886004)(6506006)(68736007)(8936002)(189998001)(575784001)(305945005)(3660700001)(86362001)(77096006)(66066001)(81156014)(39060400001)(81166006)(6116002)(2900100001)(102836003)(9686002)(5660300001)(3280700002)(92566002)(122556002)(33656002)(4326007)(3846002)(110136003)(86612001)(229853002)(76176999)(106356001)(99286002)(6916009)(8990500004)(106116001)(7736002)(50986999)(74316002)(54356999)(2906002)(6436002)(8676002)(10090500001)(101416001)(97736004)(5005710100001)(10290500002)(105586002)(76576001)(38730400001);DIR:OUT;SFP:1102;SCL:1;SRVR:CY4PR03MB2485;H:BLUPR03MB1412.namprd03.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Dec 2016 21:31:25.5901 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR03MB2485 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id uB9LjqDf009451 > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Friday, December 9, 2016 3:30 PM > To: Haiyang Zhang > Cc: Greg KH ; KY Srinivasan > ; olaf@aepfle.de; linux-kernel@vger.kernel.org; > bjorn.helgaas@gmail.com; apw@canonical.com; devel@linuxdriverproject.org; > leann.ogasawara@canonical.com; jasowang@redhat.com > Subject: Re: [PATCH 3/3] hv_netvsc: Implement VF matching based on > serial numbers > > On Fri, 9 Dec 2016 20:09:49 +0000 > Haiyang Zhang wrote: > > > > -----Original Message----- > > > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > > > Sent: Friday, December 9, 2016 1:21 PM > > > To: Greg KH > > > Cc: KY Srinivasan ; olaf@aepfle.de; Haiyang Zhang > > > ; linux-kernel@vger.kernel.org; > > > bjorn.helgaas@gmail.com; apw@canonical.com; > devel@linuxdriverproject.org; > > > leann.ogasawara@canonical.com; jasowang@redhat.com > > > Subject: Re: [PATCH 3/3] hv_netvsc: Implement VF matching based on > > > serial numbers > > > > > > On Fri, 9 Dec 2016 08:31:22 +0100 > > > Greg KH wrote: > > > > > > > On Fri, Dec 09, 2016 at 12:05:53AM +0000, KY Srinivasan wrote: > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Greg KH [mailto:gregkh@linuxfoundation.org] > > > > > > Sent: Thursday, December 8, 2016 7:56 AM > > > > > > 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; > > > > > > bjorn.helgaas@gmail.com; Haiyang Zhang > > > > > > Subject: Re: [PATCH 3/3] hv_netvsc: Implement VF matching > based on > > > serial > > > > > > numbers > > > > > > > > > > > > On Thu, Dec 08, 2016 at 12:33:43AM -0800, > > > kys@exchange.microsoft.com > > > > > > wrote: > > > > > > > From: Haiyang Zhang > > > > > > > > > > > > > > We currently use MAC address to match VF and synthetic NICs. > > > Hyper-V > > > > > > > provides a serial number to both devices for this purpose. > This > > > patch > > > > > > > implements the matching based on VF serial numbers. This is > the > > > way > > > > > > > specified by the protocol and more reliable. > > > > > > > > > > > > > > Signed-off-by: Haiyang Zhang > > > > > > > Signed-off-by: K. Y. Srinivasan > > > > > > > --- > > > > > > > drivers/net/hyperv/netvsc_drv.c | 55 > > > > > > ++++++++++++++++++++++++++++++++++++--- > > > > > > > 1 files changed, 51 insertions(+), 4 deletions(-) > > > > > > > > > > > > > > diff --git a/drivers/net/hyperv/netvsc_drv.c > > > > > > b/drivers/net/hyperv/netvsc_drv.c > > > > > > > index 9522763..c5778cf 100644 > > > > > > > --- a/drivers/net/hyperv/netvsc_drv.c > > > > > > > +++ b/drivers/net/hyperv/netvsc_drv.c > > > > > > > @@ -1165,9 +1165,10 @@ static void netvsc_free_netdev(struct > > > > > > net_device *netdev) > > > > > > > free_netdev(netdev); > > > > > > > } > > > > > > > > > > > > > > -static struct net_device *get_netvsc_bymac(const u8 *mac) > > > > > > > +static struct net_device *get_netvsc_byvfser(u32 vfser) > > > > > > > { > > > > > > > struct net_device *dev; > > > > > > > + struct net_device_context *ndev_ctx; > > > > > > > > > > > > > > ASSERT_RTNL(); > > > > > > > > > > > > > > @@ -1175,7 +1176,8 @@ static void netvsc_free_netdev(struct > > > net_device > > > > > > *netdev) > > > > > > > if (dev->netdev_ops != &device_ops) > > > > > > > continue; /* not a netvsc device */ > > > > > > > > > > > > > > - if (ether_addr_equal(mac, dev->perm_addr)) > > > > > > > + ndev_ctx = netdev_priv(dev); > > > > > > > + if (ndev_ctx->vf_serial == vfser) > > > > > > > return dev; > > > > > > > } > > > > > > > > > > > > > > @@ -1205,21 +1207,66 @@ static void > netvsc_free_netdev(struct > > > > > > net_device *netdev) > > > > > > > return NULL; > > > > > > > } > > > > > > > > > > > > > > +static u32 netvsc_get_vfser(struct net_device *vf_netdev) > > > > > > > +{ > > > > > > > + struct device *dev; > > > > > > > + struct hv_device *hdev; > > > > > > > + struct hv_pcibus_device *hbus = NULL; > > > > > > > + struct list_head *iter; > > > > > > > + struct hv_pci_dev *hpdev; > > > > > > > + unsigned long flags; > > > > > > > + u32 vfser = 0; > > > > > > > + u32 count = 0; > > > > > > > + > > > > > > > + for (dev = &vf_netdev->dev; dev; dev = dev->parent) { > > > > > > > > > > > > You are going to walk the whole device tree backwards? That's > > > crazy. > > > > > > And foolish. And racy and broken (what happens if the tree > > > changes > > > > > > while you do this?) Where is the lock being grabbed while > this > > > happens? > > > > > > What about reference counts? Do you see other drivers ever > doing > > > this > > > > > > (if you do, point them out and I'll go yell at them too...) > > > > > > > > > > Greg, > > > > > > > > > > We are registering for netdev events. Coming into this function, > the > > > caller > > > > > guarantees that the list of netdevs does not change - we assert > this > > > on entry: > > > > > ASSERT_RTNL(). We are only walking up the device tree for the > > > netdevs whose > > > > > state change is being notified to us - the device tree being > walked > > > here is limited to > > > > > netdevs under question. > > > > > > > > But a netdev is a child of some type of "real" device, and you are > now > > > > walking the tree of all devices up to the "root" parent device, > which > > > > means you will hit PCI bridges, USB controllers, and all sorts of > fun > > > > things if you are a child of those types of devices. > > > > > > > > And can't you tell if the netdev for this event, really is "your" > > > > netdev? Or are you getting called this for "all" netdevs? Sorry, > I > > > > don't know this api, any pointers to it would be appreciated. > > > > > > > > > We have a reference to the device and we know the device is not > > > going away. Is it not > > > > > safe to dereference the parent pointer - after all the child has > > > taken a reference on > > > > > the parent as part of device_add() call. > > > > > > > > It might be, and might not be. There's a reason you don't see > this > > > > pattern anywhere in the kernel because of this... > > > > > > > > > > > + if (!dev_is_vmbus(dev)) > > > > > > > + continue; > > > > > > > > > > > > Ick. > > > > > > > > > > > > Why isn't your parent pointer a vmbus device all the time? > How > > > could > > > > > > you get burried down in the device hierarchy when you are the > > > driver for > > > > > > a specific bus type in the first place? How could this > function > > > ever be > > > > > > called for a device that is NOT of this type? > > > > > > > > > > We get notified when state changes on any of the netdev devices > in > > > the system. > > > > > Not all netdevs in the system belong to vmbus. Consider for > instance > > > the > > > > > emulated NIC that can be configured. This is an emulated PCI NIC. > We > > > are only > > > > > interested in netdevs that correspond to the VF instance that we > are > > > interested in. > > > > > > > > Can you "know" this is your netdev by some other way than having > to > > > walk > > > > the device tree? Name? local device type? Something else? This > > > seems > > > > like an odd api in that everyone would have to do gyrations like > this > > > in > > > > order to determine if the netdev is "theirs" or not... > > > > > > The scenario is SR-IOV on Hyper-V. In the case of VF device, the > host > > > hands the > > > guest OS a PCI device for the virtual function device. The VF device > is > > > placed > > > on a special synthetic PCI bus (ie not part of the other buses on > the > > > system). > > > The VF device also has a synthetic network interface (netvsc) which > > > lives > > > on VMBUS. This code is about managing the interaction between the > two. > > > > > > The association between VF and synthetic NIC is done in response to > the > > > VF network device being registered. Initial version was based on MAC > > > address > > > which is the same. Later refinement used permanent MAC address to > > > avoid bugs if MAC address changed. This version is to use serial > number > > > instead which is safer than MAC address. > > > > > > The code to walk up/down maybe not be needed to find serial number. > > > Perhaps a more direct single set of conditions is possible? > > > > > > Something like: > > > > > > In pci-hyperv.c > > > > > > u32 hv_pcifront_get_serial(struct pci_bus *bus, unsigned int devfn) > > > { > > > struct hv_pcibus_device *hbus > > > = container_of(bus->sysdata, > > > struct hv_pcibus_device, sysdata); > > > struct hf_pci_dev *hpdev; > > > u32 serial; > > > > > > hpdev = get_pcichild_wslot(hbus, devfn_to_wslot(pdev->devfn)); > > > if (!hpdev) > > > return 0; > > > > > > serial = hpdev->devs.ser; > > > put_pcichild(hpdev, hv_pcidev_ref_by_slot); > > > return serial; > > > } > > > > > > In netvsc_drv.c > > > > > > static u32 netvsc_get_vfser(struct net_device *vf_netdev) > > > { > > > struct device *dev = vf_netdev->dev.parent; > > > struct pci_dev *pdev; > > > u32 wslot; > > > > > > if (!dev || !dev_is_pci(dev)) > > > return 0; > > > > > > pdev = container_of(dev, struct pci_device, dev); > > > > > > return hv_pcifront_get_serial(pdev->bus, pdev->devfn); > > > } > > > > > > > > > > > > > > > > > > P.S: it would be good to be able to get win_slot out through sysfs > as > > > well for systemd/udev. > > > > Stephen, > > > > Thanks for suggestion. Actually, in my earlier implementation of this > > feature (VF serial based matching), I thought about export a function > > from vPCI driver, then calling it from netvsc. So I don't need to > > move structs between headers... But, it creates a dependency of netvsc > > on vPCI driver's symbol. So, even if on a VM without SRIOV, we have to > > load vPCI driver, which we don't want. > > > > Also, hv_vpci device is 3 parent layers above the vf_netdevice: > > Here is the VF drv hierarchy -- > > Should we assume it's always 3 parents above vf_netdevice, or search > for it? > > > > [ 368.185259] HZINFO:NETDEV_REGISTER: > > [ 368.185261] HZINFO: dev:ffff88007c10d518, bus: (null), > busName:(null), drvName:(null) > > [ 368.185262] HZINFO: dev:ffff88007c10c0a0, bus:ffffffff81ce4b60, > busName:pci, drvName:ixgbevf > > [ 368.185263] HZINFO: dev:ffff8800355c0000, bus: (null), > busName:(null), drvName:(null) > > [ 368.185264] HZINFO: dev:ffff8800355c5428, bus:ffffffffa0008160, > busName:vmbus, drvName:hv_pci > > [ 368.185264] HZINFO: dev:ffff88007c49e268, bus:ffffffff81ce9800, > busName:acpi, drvName:vmbus > > [ 368.185265] HZINFO: dev:ffff88007c48ea68, bus:ffffffff81ce9800, > busName:acpi, drvName:(null) > > [ 368.185266] HZINFO: dev:ffff88007c48aa68, bus:ffffffff81ce9800, > busName:acpi, drvName:(null) > > [ 368.185266] HZINFO: dev:ffff88007c48a268, bus:ffffffff81ce9800, > busName:acpi, drvName:(null) > > [ 368.185267] HZINFO: dev:ffff88007c489a68, bus:ffffffff81ce9800, > busName:acpi, drvName:(null) > > > > Thanks, > > - Haiyang > > Since this is a synthetic bus, the topology should not change unless > host side > software changes. The vf_netdev device has to be PCI device, so that is > going to > be certain. After that there maybe intermediate up to hv_pci. The code > in hyperv-pci > already has similar stuff (ie for read_config). Other netdevice, like emulated NIC can also trigger this notification. They are not vPCI. Thanks, - Haiyang