linux-kernel - [PATCH 0/2] Drivers: hv: vmbus: Change memory-mapped I/O management for Hyper-V paravirt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1435703668-23486-1-git-send-email-kys@microsoft.com>
Date:	Tue, 30 Jun 2015 15:34:28 -0700
From:	"K. Y. Srinivasan" <kys@...rosoft.com>
To:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	vkuznets@...hat.com, jasowang@...hat.com, hdegoede@...hat.com,
	linux-fbdev@...r.kernel.org, haiyangz@...rosoft.com
Cc:	"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: [PATCH 0/2] Drivers: hv: vmbus: Change memory-mapped I/O management for Hyper-V paravirt 

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@...rosoft.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/