From: "K. Y. Srinivasan" <kys@microsoft.com>
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" <kys@microsoft.com>
Subject: [PATCH 0/2] Drivers: hv: vmbus: Change memory-mapped I/O management for Hyper-V paravirt
Date: Tue, 30 Jun 2015 21:19:01 +0000 [thread overview]
Message-ID: <1435703668-23486-1-git-send-email-kys@microsoft.com> (raw)
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
next reply other threads:[~2015-06-30 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:19 K. Y. Srinivasan [this message]
2015-06-30 21:12 ` [PATCH 1/2] drivers:hv: Modify hv_vmbus to search for all MMIO ranges available K. Y. Srinivasan
2015-06-30 21:12 ` [PATCH 2/2] drivers:hv: Move MMIO range picking from hyper_fb to hv_vmbus K. Y. Srinivasan
2015-07-01 8:00 ` [PATCH 1/2] drivers:hv: Modify hv_vmbus to search for all MMIO ranges available Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1435703668-23486-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=hdegoede@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).