From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework Date: Wed, 25 Apr 2018 17:18:31 -0700 Message-ID: <20180425171831.785f412b@xeon-e3> References: <1524188524-28411-5-git-send-email-sridhar.samudrala@intel.com> <20180420082802.6ca37e4c@xeon-e3> <20180420160058.GB2150@nanopsycho.orion> <20180423100406.71b95f74@xeon-e3> <20180423202204-mutt-send-email-mst@kernel.org> <20180423104440.2fe6cfd2@xeon-e3> <20180423205019-mutt-send-email-mst@kernel.org> <20180423230037-mutt-send-email-mst@kernel.org> <20180426011221-mutt-send-email-mst@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , Jiri Pirko , Sridhar Samudrala , David Miller , Netdev , virtualization@lists.linux-foundation.org, virtio-dev@lists.oasis-open.org, "Brandeburg, Jesse" , Alexander Duyck , Jakub Kicinski , Jason Wang To: Siwei Liu Return-path: Received: from mail-pg0-f65.google.com ([74.125.83.65]:46795 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105AbeDZASe (ORCPT ); Wed, 25 Apr 2018 20:18:34 -0400 Received: by mail-pg0-f65.google.com with SMTP id z4so1605273pgu.13 for ; Wed, 25 Apr 2018 17:18:34 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 25 Apr 2018 15:57:57 -0700 Siwei Liu wrote: > > > > I think ideally the infrastructure should suppport flexible matching of > > NICs - netvsc is already reported to be moving to some kind of serial > > address. > > > As Stephen said, Hyper-V supports the serial UUID thing from day-one. > It's just the Linux netvsc guest driver itself does not leverage that > ID from the very beginging. > > Regards, > -Siwei I am working on that. The problem is that it requires some messy work to go from VF netdevice back to PCI device and from there to the PCI hyperv host infrastructure to find the serial number. I was hoping that the serial number would also match the concept of PCI Express device serial number. But that is a completely different ID :-( The PCI-E serial number is a hardware serial number more like MAC address. The Hyper-V serial number is more like PCI slot value.