From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752852AbbF3VLg (ORCPT ); Tue, 30 Jun 2015 17:11:36 -0400 Received: from p3plsmtps2ded03.prod.phx3.secureserver.net ([208.109.80.60]:37253 "EHLO p3plsmtps2ded03.prod.phx3.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752479AbbF3VL2 (ORCPT ); Tue, 30 Jun 2015 17:11:28 -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, hdegoede@redhat.com, linux-fbdev@vger.kernel.org, haiyangz@microsoft.com Cc: "K. Y. Srinivasan" Subject: [PATCH 0/2] Drivers: hv: vmbus: Change memory-mapped I/O management for Hyper-V paravirt Date: Tue, 30 Jun 2015 15:34:28 -0700 Message-Id: <1435703668-23486-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 This patch series changes the way that hv_vmbus searches for ranges of memory-mapped I/O space (MMIO) which can be used by its children. The old way just found the one and only range above 4GB. This one makes all ranges exposed in the VM's firmware potential candidates. It also moves the code which chooses ranges from hyperv_fb (the video front-end driver for Hyper-V) to hv_vmbus. jakeo@microsoft.com (2): drivers:hv: Modify hv_vmbus to search for all MMIO ranges available. drivers:hv: Move MMIO range picking from hyper_fb to hv_vmbus drivers/hv/vmbus_drv.c | 204 +++++++++++++++++++++++++++++++++------ drivers/video/fbdev/hyperv_fb.c | 46 ++++----- include/linux/hyperv.h | 7 +- 3 files changed, 200 insertions(+), 57 deletions(-) -- 1.7.4.1