From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935499AbcA0WvR (ORCPT ); Wed, 27 Jan 2016 17:51:17 -0500 Received: from p3plsmtps2ded04.prod.phx3.secureserver.net ([208.109.80.198]:59146 "EHLO p3plsmtps2ded04.prod.phx3.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934500AbcA0Wud (ORCPT ); Wed, 27 Jan 2016 17:50:33 -0500 x-originating-ip: 72.167.245.219 From: "K. Y. Srinivasan" To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com, jasowang@redhat.com Cc: Dexuan Cui , "K. Y. Srinivasan" Subject: [PATCH 09/13] Drivers: hv: vmbus: add a hvsock flag in struct hv_driver Date: Wed, 27 Jan 2016 16:26:51 -0800 Message-Id: <1453940815-26096-9-git-send-email-kys@microsoft.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1453940815-26096-1-git-send-email-kys@microsoft.com> References: <1453940792-25878-1-git-send-email-kys@microsoft.com> <1453940815-26096-1-git-send-email-kys@microsoft.com> X-CMAE-Envelope: MS4wfAiF4ExqZEGHqmLZQEDdkEZzA+KBT+ouoIL8qTl1EC0lzGw9aMo8u0IGQlLughkDtS7jCz2inKJ4mcMZdC7DQRmZNSInOYY9NGggl3nsstnbubIdbMpW r+0YVQOyLRzjdyE/48PVVK3Sn2hMb5PB4290JhwDCLy7KfMD6q6BifC9gfoiZss0txBy06tCsSI0XeMHKMb8FHTbJPgSKWaHm//WkaDOnHdjXCKJykzHDzFL WlpYM+I9bUmAF0rr0nmMCtEb9QpdfTzKdN55b6d+gKutwDT0ujmw1SR3xSE+mGp/VQ+h2wtEZnuOOG6NVp9+xJaNCuSbbKZaRILQ5q58K4EsmUs+Ymn0QOJ/ R6ytJap1zCl6VeKZOrHzree3lIvZrh3bvUn3hI4g8KPloGz9l7MUWPISl1YPAQygHtC9Etasg7c5grTlFQTdBHasxWRvDA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Dexuan Cui 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 Signed-off-by: K. Y. Srinivasan --- drivers/hv/vmbus_drv.c | 4 ++++ include/linux/hyperv.h | 14 ++++++++++++++ 2 files changed, 18 insertions(+), 0 deletions(-) diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c index 3668a95..063e5f5 100644 --- a/drivers/hv/vmbus_drv.c +++ b/drivers/hv/vmbus_drv.c @@ -582,6 +582,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 898eac9..f636f91 100644 --- a/include/linux/hyperv.h +++ b/include/linux/hyperv.h @@ -990,6 +990,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; -- 1.7.4.1