Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754230AbbGTCMq (ORCPT ); Sun, 19 Jul 2015 22:12:46 -0400 Received: from p3plsmtps2ded04.prod.phx3.secureserver.net ([208.109.80.198]:58713 "EHLO p3plsmtps2ded04.prod.phx3.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753947AbbGTCMp (ORCPT ); Sun, 19 Jul 2015 22:12:45 -0400 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: "K. Y. Srinivasan" Subject: [PATCH 0/5] Drivers: hv: vmbus: Miscellaneous improvements and fixes Date: Sun, 19 Jul 2015 20:36:59 -0700 Message-Id: <1437363419-3511-1-git-send-email-kys@microsoft.com> X-Mailer: git-send-email 1.7.4.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1177 Lines: 32 In addition to a bug fix and some improvements to the way we distribute channel load amongst available CPUs, this patch set also includes an implementation of a clocksource based on the TSC page that Hyper-V supports. Christopher Oo (1): Drivers: hv_vmbus: Fix signal to host condition Dexuan Cui (1): Drivers: hv: vmbus: Further improve CPU affiliation logic K. Y. Srinivasan (2): Drivers: hv: vmbus: Improve the CPU affiliation for channels Drivers: hv: vmbus: Implement a clocksource based on the TSC page Viresh Kumar (1): drivers/hv: Migrate to new 'set-state' interface arch/x86/include/uapi/asm/hyperv.h | 2 + drivers/hv/channel_mgmt.c | 29 +++++++-- drivers/hv/hv.c | 120 ++++++++++++++++++++++++++++-------- drivers/hv/hyperv_vmbus.h | 14 ++++ drivers/hv/ring_buffer.c | 14 +--- 5 files changed, 136 insertions(+), 43 deletions(-) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/