From patchwork Tue Jan 26 09:44:52 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dexuan Cui X-Patchwork-Id: 573119 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 2A15B140216 for ; Tue, 26 Jan 2016 19:10:30 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933070AbcAZIKL (ORCPT ); Tue, 26 Jan 2016 03:10:11 -0500 Received: from p3plsmtps2ded01.prod.phx3.secureserver.net ([208.109.80.58]:56653 "EHLO p3plsmtps2ded01.prod.phx3.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933042AbcAZIIe (ORCPT ); Tue, 26 Jan 2016 03:08:34 -0500 Received: from linuxonhyperv.com ([72.167.245.219]) by : HOSTING RELAY : with SMTP id NyfxaTcIUzzCiNyfxa9OMI; Tue, 26 Jan 2016 01:08:34 -0700 x-originating-ip: 72.167.245.219 Received: by linuxonhyperv.com (Postfix, from userid 518) id B556619025B; Tue, 26 Jan 2016 01:44:52 -0800 (PST) From: Dexuan Cui To: gregkh@linuxfoundation.org, davem@davemloft.net, stephen@networkplumber.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, driverdev-devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com, kys@microsoft.com, vkuznets@redhat.com Cc: pebolle@tiscali.nl, stefanha@redhat.com, dan.carpenter@oracle.com Subject: [PATCH V6 5/8] Drivers: hv: vmbus: add a hvsock flag in struct hv_driver Date: Tue, 26 Jan 2016 01:44:52 -0800 Message-Id: <1453801492-3397-1-git-send-email-decui@microsoft.com> X-Mailer: git-send-email 1.7.4.1 X-CMAE-Envelope: MS4wfGbjaUCG0LHa4jUOlawVpkcuE7j7tIhV4GxtRy5cb+Tpyjk/GOHO0PTMnNneHr4TMZrKlypRRAQHPiLLee8lnZaaaNiUz9PbjFBDJNz9R5U4C+uQ6Urj 7YbzptOVyc5kBavpG1/xcsH/0fEwP2Cc/cxsL0bEv1xYF6/L6/QF/LQsCI2COhbYSOmHLbY+yll3zyz6VngDthCg5pnRpL4QUhTC46cLhIvdAdL24p4Swm6v 5wqnFLMsOQRnOXnC8/f/AuMdMjfL+AYsaqbMkGhqoE5XTtO8bAJJHz0jxGHepO8uskUQXUY9kI6uBZ4dHiQ4TFideceavxEq2MGI1IqZr1xYTo1p87ua8+9Q bK5+S5uKL9IHka/gREVubbpHvYf1kaa5OAkYE9/ivvg8bwkccNzMAPdqSleM4yiblsASj6fyhuxMiyfWLA3IxjqZQQbgEOK+AR3gJDodRXh/EetVLJQcXGKi skQdeHgKB/xSQznevMAco8S+lwI27NihbyI0IHF1vIgd6RIIOpoAV9MyZgSQIpzK6W8EWhLheHBnBof5y2QDjRxk5R0nikBYxx8ItSIltRe5PaDztBZC8z6V s+SN81MpfgEKscrterM2HGVJAkUNmrLOPE5+E8533R6I9A== Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Only the coming hv_sock driver has a "true" value for this flag. We treat the hvsock offers/channels as special VMBus devices. Since the hv_sock driver handles all the hvsock offers/channels, we need to tweak vmbus_match() for hv_sock driver, so we introduce this flag. Signed-off-by: Dexuan Cui --- drivers/hv/vmbus_drv.c | 4 ++++ include/linux/hyperv.h | 14 ++++++++++++++ 2 files changed, 18 insertions(+) diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c index 328e4c3..c1c9d71 100644 --- a/drivers/hv/vmbus_drv.c +++ b/drivers/hv/vmbus_drv.c @@ -562,6 +562,10 @@ static int vmbus_match(struct device *device, struct device_driver *driver) struct hv_driver *drv = drv_to_hv_drv(driver); struct hv_device *hv_dev = device_to_hv_device(device); + /* The hv_sock driver handles all hv_sock offers. */ + if (is_hvsock_channel(hv_dev->channel)) + return drv->hvsock; + if (hv_vmbus_get_id(drv->id_table, &hv_dev->dev_type)) return 1; diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index b835d80..5587711 100644 --- a/include/linux/hyperv.h +++ b/include/linux/hyperv.h @@ -964,6 +964,20 @@ extern void vmbus_ontimer(unsigned long data); struct hv_driver { const char *name; + /* + * A hvsock offer, which has a VMBUS_CHANNEL_TLNPI_PROVIDER_OFFER + * channel flag, actually doesn't mean a synthetic device because the + * offer's if_type/if_instance can change for every new hvsock + * connection. + * + * However, to facilitate the notification of new-offer/rescind-offer + * from vmbus driver to hvsock driver, we can handle hvsock offer as + * a special vmbus device, and hence we need the below flag to + * indicate if the driver is the hvsock driver or not: we need to + * specially treat the hvosck offer & driver in vmbus_match(). + */ + bool hvsock; + /* the device type supported by this driver */ uuid_le dev_type; const struct hv_vmbus_device_id *id_table;