Skip to contentSkip to conversation

Drivers: hv: vmbus: Cleanup and mmio management.

PATCH In review K. Y. Srinivasan 3 participants 13 messages Apr 2, 2016 – Apr 4, 2016

Subsystems (3)
PCI Framebuffer layer Hyper-V/Azure core and drivers
lore
Share & tools
lore

K. Y. Srinivasan

author
#0 lore raw

cover Drivers: hv: vmbus: Cleanup and mmio management.

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

Jake Oshins (5):
hv: Make a function to free mmio regions through vmbus
hv: Lock access to hyperv_mmio resource tree
hv: Use new vmbus_mmio_free() from client drivers.
hv: Reverse order of resources in hyperv_mmio
hv: Track allocations of children of hv_vmbus in private resource
tree

Vitaly Kuznetsov (1):
Drivers: hv: kvp: fix IP Failover

 drivers/hv/hv_kvp.c             |   31 +++++++++++++++++++++
 drivers/hv/hyperv_vmbus.h       |    5 +++
 drivers/hv/vmbus_drv.c          |   56 ++++++++++++++++++++++++++++++++++-----
 drivers/pci/host/pci-hyperv.c   |   14 +++++-----
 drivers/video/fbdev/hyperv_fb.c |    4 +-
 include/linux/hyperv.h          |    2 +-
 6 files changed, 95 insertions(+), 17 deletions(-)
Signature · 1 line
1.7.4.1
author
#1 lore raw

PATCH 1/6 Drivers: hv: kvp: fix IP Failover

From: Vitaly Kuznetsov <[email protected]>

Hyper-V VMs can be replicated to another hosts and there is a feature to set different IP for replicas, it is called 'Failover TCP/IP'. When such guest starts Hyper-V host sends it KVP_OP_SET_IP_INFO message as soon as we finish negotiation procedure. The problem is that it can happen (and it actually happens) before userspace daemon connects and we reply with HV_E_FAIL to the message. As there are no repetitions we fail to set the requested IP.

Solve the issue by postponing our reply to the negotiation message till userspace daemon is connected. We can't wait too long as there is a host-side timeout (cca. 75 seconds) and if we fail to reply in this time frame the whole KVP service will become inactive. The solution is not ideal - if it takes userspace daemon more than 60 seconds to connect IP Failover will still fail but I don't see a solution with our current separation between kernel and userspace parts.

Other two modules (VSS and FCOPY) don't require such delay, leave them untouched.

Signed-off-by Vitaly Kuznetsov <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/hv/hv_kvp.c       |   31 +++++++++++++++++++++++++++++++
 drivers/hv/hyperv_vmbus.h |    5 +++++
 2 files changed, 36 insertions(+), 0 deletions(-)
drivers/hv/hv_kvp.c +31 -0
index 9b9b370..cb1a916 100644
@@ -78,9 +78,11 @@ static void kvp_send_key(struct work_struct *dummy);
 
 static void kvp_respond_to_host(struct hv_kvp_msg *msg, int error);
 static void kvp_timeout_func(struct work_struct *dummy);
+static void kvp_host_handshake_func(struct work_struct *dummy);
 static void kvp_register(int);
 
 static DECLARE_DELAYED_WORK(kvp_timeout_work, kvp_timeout_func);
+static DECLARE_DELAYED_WORK(kvp_host_handshake_work, kvp_host_handshake_func);
 static DECLARE_WORK(kvp_sendkey_work, kvp_send_key);
 
 static const char kvp_devname[] = "vmbus/hv_kvp";

@@ -130,6 +132,11 @@ static void kvp_timeout_func(struct work_struct *dummy)
 	hv_poll_channel(kvp_transaction.recv_channel, kvp_poll_wrapper);
 }
 
+static void kvp_host_handshake_func(struct work_struct *dummy)
+{
+	hv_poll_channel(kvp_transaction.recv_channel, hv_kvp_onchannelcallback);
+}
+
 static int kvp_handle_handshake(struct hv_kvp_msg *msg)
 {
 	switch (msg->kvp_hdr.operation) {

@@ -154,6 +161,12 @@ static int kvp_handle_handshake(struct hv_kvp_msg *msg)
 	pr_debug("KVP: userspace daemon ver. %d registered\n",
 		 KVP_OP_REGISTER);
 	kvp_register(dm_reg_value);
+
+	/*
+	 * If we're still negotiating with the host cancel the timeout
+	 * work to not poll the channel twice.
+	 */
+	cancel_delayed_work_sync(&kvp_host_handshake_work);
 	hv_poll_channel(kvp_transaction.recv_channel, kvp_poll_wrapper);
 
 	return 0;

@@ -594,7 +607,22 @@ void hv_kvp_onchannelcallback(void *context)
 	struct icmsg_negotiate *negop = NULL;
 	int util_fw_version;
 	int kvp_srv_version;
+	static enum {NEGO_NOT_STARTED,
+		     NEGO_IN_PROGRESS,
+		     NEGO_FINISHED} host_negotiatied = NEGO_NOT_STARTED;
 
+	if (host_negotiatied == NEGO_NOT_STARTED &&
+	    kvp_transaction.state < HVUTIL_READY) {
+		/*
+		 * If userspace daemon is not connected and host is asking
+		 * us to negotiate we need to delay to not lose messages.
+		 * This is important for Failover IP setting.
+		 */
+		host_negotiatied = NEGO_IN_PROGRESS;
+		schedule_delayed_work(&kvp_host_handshake_work,
+				      HV_UTIL_NEGO_TIMEOUT * HZ);
+		return;
+	}
 	if (kvp_transaction.state > HVUTIL_READY)
 		return;
 

@@ -672,6 +700,8 @@ void hv_kvp_onchannelcallback(void *context)
 		vmbus_sendpacket(channel, recv_buffer,
 				       recvlen, requestid,
 				       VM_PKT_DATA_INBAND, 0);
+
+		host_negotiatied = NEGO_FINISHED;
 	}
 
 }

@@ -708,6 +738,7 @@ hv_kvp_init(struct hv_util_service *srv)
 void hv_kvp_deinit(void)
 {
 	kvp_transaction.state = HVUTIL_DEVICE_DYING;
+	cancel_delayed_work_sync(&kvp_host_handshake_work);
 	cancel_delayed_work_sync(&kvp_timeout_work);
 	cancel_work_sync(&kvp_sendkey_work);
 	hvutil_transport_destroy(hvt);
drivers/hv/hyperv_vmbus.h +5 -0
index 12321b9..8b07f9c 100644
@@ -36,6 +36,11 @@
 #define HV_UTIL_TIMEOUT 30
 
 /*
+ * Timeout for guest-host handshake for services.
+ */
+#define HV_UTIL_NEGO_TIMEOUT 60
+
+/*
  * The below CPUID leaves are present if VersionAndFeatures.HypervisorPresent
  * is set by CPUID(HVCPUID_VERSION_FEATURES).
  */
Signature · 1 line
1.7.4.1
author
#2 lore raw

PATCH 2/6 hv: Make a function to free mmio regions through vmbus

From: Jake Oshins <[email protected]>

This patch introduces a function that reverses everything done by vmbus_allocate_mmio(). Existing code just called release_mem_region(). Future patches in this series require a more complex sequence of actions, so this function is introduced to wrap those actions.

Signed-off-by Jake Oshins <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/hv/vmbus_drv.c |   15 +++++++++++++++
 include/linux/hyperv.h |    2 +-
 2 files changed, 16 insertions(+), 1 deletions(-)
drivers/hv/vmbus_drv.c +15 -0
index 64713ff..44e95a4 100644
@@ -1180,6 +1180,21 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 EXPORT_SYMBOL_GPL(vmbus_allocate_mmio);
 
 /**
+ * vmbus_free_mmio() - Free a memory-mapped I/O range.
+ * @start:		Base address of region to release.
+ * @size:		Size of the range to be allocated
+ *
+ * This function releases anything requested by
+ * vmbus_mmio_allocate().
+ */
+void vmbus_free_mmio(resource_size_t start, resource_size_t size)
+{
+	release_mem_region(start, size);
+
+}
+EXPORT_SYMBOL_GPL(vmbus_free_mmio);
+
+/**
  * vmbus_cpu_number_to_vp_number() - Map CPU to VP.
  * @cpu_number: CPU number in Linux terms
  *
include/linux/hyperv.h +1 -1
index aa0fadc..ecd81c3 100644
@@ -1091,7 +1091,7 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 			resource_size_t min, resource_size_t max,
 			resource_size_t size, resource_size_t align,
 			bool fb_overlap_ok);
-
+void vmbus_free_mmio(resource_size_t start, resource_size_t size);
 int vmbus_cpu_number_to_vp_number(int cpu_number);
 u64 hv_do_hypercall(u64 control, void *input, void *output);
Signature · 1 line
1.7.4.1
author
#3 lore raw

PATCH 3/6 hv: Lock access to hyperv_mmio resource tree

In reply to K. Y. Srinivasan

From: Jake Oshins <[email protected]>

In existing code, this tree of resources is created in single-threaded code and never modified after it is created, and thus needs no locking. This patch introduces a semaphore for tree access, as other patches in this series introduce run-time modifications of this resource tree which can happen on multiple threads.

Signed-off-by Jake Oshins <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/hv/vmbus_drv.c |   16 ++++++++++++----
 1 files changed, 12 insertions(+), 4 deletions(-)
drivers/hv/vmbus_drv.c +12 -4
index 44e95a4..60553c1 100644
@@ -102,6 +102,7 @@ static struct notifier_block hyperv_panic_block = {
 };
 
 struct resource *hyperv_mmio;
+DEFINE_SEMAPHORE(hyperv_mmio_lock);
 
 static int vmbus_exists(void)
 {

@@ -1132,7 +1133,10 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 	resource_size_t range_min, range_max, start, local_min, local_max;
 	const char *dev_n = dev_name(&device_obj->device);
 	u32 fb_end = screen_info.lfb_base + (screen_info.lfb_size << 1);
-	int i;
+	int i, retval;
+
+	retval = -ENXIO;
+	down(&hyperv_mmio_lock);
 
 	for (iter = hyperv_mmio; iter; iter = iter->sibling) {
 		if ((iter->start >= max) || (iter->end <= min))

@@ -1169,13 +1173,17 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 			for (; start + size - 1 <= local_max; start += align) {
 				*new = request_mem_region_exclusive(start, size,
 								    dev_n);
-				if (*new)
-					return 0;
+				if (*new) {
+					retval = 0;
+					goto exit;
+				}
 			}
 		}
 	}
 
-	return -ENXIO;
+exit:
+	up(&hyperv_mmio_lock);
+	return retval;
 }
 EXPORT_SYMBOL_GPL(vmbus_allocate_mmio);
Signature · 1 line
1.7.4.1
author
#4 lore raw

PATCH 4/6 hv: Use new vmbus_mmio_free() from client drivers.

In reply to K. Y. Srinivasan

From: Jake Oshins <[email protected]>

This patch modifies all the callers of vmbus_mmio_allocate() to call vmbus_mmio_free() instead of release_mem_region().

Signed-off-by Jake Oshins <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/pci/host/pci-hyperv.c   |   14 +++++++-------
 drivers/video/fbdev/hyperv_fb.c |    4 ++--
 2 files changed, 9 insertions(+), 9 deletions(-)
drivers/pci/host/pci-hyperv.c +7 -7
index ed651ba..f2559b6 100644
@@ -1795,14 +1795,14 @@ static void hv_pci_free_bridge_windows(struct hv_pcibus_device *hbus)
 
 	if (hbus->low_mmio_space && hbus->low_mmio_res) {
 		hbus->low_mmio_res->flags |= IORESOURCE_BUSY;
-		release_mem_region(hbus->low_mmio_res->start,
-				   resource_size(hbus->low_mmio_res));
+		vmbus_free_mmio(hbus->low_mmio_res->start,
+				resource_size(hbus->low_mmio_res));
 	}
 
 	if (hbus->high_mmio_space && hbus->high_mmio_res) {
 		hbus->high_mmio_res->flags |= IORESOURCE_BUSY;
-		release_mem_region(hbus->high_mmio_res->start,
-				   resource_size(hbus->high_mmio_res));
+		vmbus_free_mmio(hbus->high_mmio_res->start,
+				resource_size(hbus->high_mmio_res));
 	}
 }
 

@@ -1880,8 +1880,8 @@ static int hv_pci_allocate_bridge_windows(struct hv_pcibus_device *hbus)
 
 release_low_mmio:
 	if (hbus->low_mmio_res) {
-		release_mem_region(hbus->low_mmio_res->start,
-				   resource_size(hbus->low_mmio_res));
+		vmbus_free_mmio(hbus->low_mmio_res->start,
+				resource_size(hbus->low_mmio_res));
 	}
 
 	return ret;

@@ -1924,7 +1924,7 @@ static int hv_allocate_config_window(struct hv_pcibus_device *hbus)
 
 static void hv_free_config_window(struct hv_pcibus_device *hbus)
 {
-	release_mem_region(hbus->mem_config->start, PCI_CONFIG_MMIO_LENGTH);
+	vmbus_free_mmio(hbus->mem_config->start, PCI_CONFIG_MMIO_LENGTH);
 }
 
 /**
drivers/video/fbdev/hyperv_fb.c +2 -2
index e2451bd..2fd49b2 100644
@@ -743,7 +743,7 @@ static int hvfb_getmem(struct hv_device *hdev, struct fb_info *info)
 err3:
 	iounmap(fb_virt);
 err2:
-	release_mem_region(par->mem->start, screen_fb_size);
+	vmbus_free_mmio(par->mem->start, screen_fb_size);
 	par->mem = NULL;
 err1:
 	if (!gen2vm)

@@ -758,7 +758,7 @@ static void hvfb_putmem(struct fb_info *info)
 	struct hvfb_par *par = info->par;
 
 	iounmap(info->screen_base);
-	release_mem_region(par->mem->start, screen_fb_size);
+	vmbus_free_mmio(par->mem->start, screen_fb_size);
 	par->mem = NULL;
 }
Signature · 1 line
1.7.4.1
author
#5 lore raw

PATCH 5/6 hv: Reverse order of resources in hyperv_mmio

In reply to K. Y. Srinivasan

From: Jake Oshins <[email protected]>

A patch later in this series allocates child nodes in this resource tree. For that to work, this tree needs to be sorted in ascending order.

Signed-off-by Jake Oshins <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/hv/vmbus_drv.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)
drivers/hv/vmbus_drv.c +1 -2
index 60553c1..1ce47d0 100644
@@ -1049,7 +1049,6 @@ static acpi_status vmbus_walk_resources(struct acpi_resource *res, void *ctx)
 	new_res->end = end;
 
 	/*
-	 * Stick ranges from higher in address space at the front of the list.
 	 * If two ranges are adjacent, merge them.
 	 */
 	do {

@@ -1070,7 +1069,7 @@ static acpi_status vmbus_walk_resources(struct acpi_resource *res, void *ctx)
 			break;
 		}
 
-		if ((*old_res)->end < new_res->start) {
+		if ((*old_res)->start > new_res->end) {
 			new_res->sibling = *old_res;
 			if (prev_res)
 				(*prev_res)->sibling = new_res;
Signature · 1 line
1.7.4.1
author
#6 lore raw

PATCH 6/6 hv: Track allocations of children of hv_vmbus in private resource tree

In reply to K. Y. Srinivasan

From: Jake Oshins <[email protected]>

This patch changes vmbus_allocate_mmio() and vmbus_free_mmio() so that when child paravirtual devices allocate memory-mapped I/O space, they allocate it privately from a resource tree pointed at by hyperv_mmio and also by the public resource tree iomem_resource. This allows the region to be marked as "busy" in the private tree, but a "bridge window" in the public tree, guaranteeing that no two bridge windows will overlap each other but while also allowing the PCI device children of the bridge windows to overlap that window.

One might conclude that this belongs in the pnp layer, rather than in this driver. Rafael Wysocki, the maintainter of the pnp layer, has previously asked that we not modify the pnp layer as it is considered deprecated. This patch is thus essentially a workaround.

Signed-off-by Jake Oshins <[email protected]>
Signed-off-by K. Y. Srinivasan <[email protected]>
---
 drivers/hv/vmbus_drv.c |   22 +++++++++++++++++++++-
 1 files changed, 21 insertions(+), 1 deletions(-)
drivers/hv/vmbus_drv.c +21 -1
index 1ce47d0..dfc6149 100644
@@ -1128,7 +1128,7 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 			resource_size_t size, resource_size_t align,
 			bool fb_overlap_ok)
 {
-	struct resource *iter;
+	struct resource *iter, *shadow;
 	resource_size_t range_min, range_max, start, local_min, local_max;
 	const char *dev_n = dev_name(&device_obj->device);
 	u32 fb_end = screen_info.lfb_base + (screen_info.lfb_size << 1);

@@ -1170,12 +1170,22 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
 
 			start = (local_min + align - 1) & ~(align - 1);
 			for (; start + size - 1 <= local_max; start += align) {
+				shadow = __request_region(iter, start,
+							  size,
+							  NULL,
+							  IORESOURCE_BUSY);
+				if (!shadow)
+					continue;
+
 				*new = request_mem_region_exclusive(start, size,
 								    dev_n);
 				if (*new) {
+					shadow->name = (char *)*new;
 					retval = 0;
 					goto exit;
 				}
+
+				__release_region(iter, start, size);
 			}
 		}
 	}

@@ -1196,7 +1206,17 @@ EXPORT_SYMBOL_GPL(vmbus_allocate_mmio);
  */
 void vmbus_free_mmio(resource_size_t start, resource_size_t size)
 {
+	struct resource *iter;
+
+	down(&hyperv_mmio_lock);
+	for (iter = hyperv_mmio; iter; iter = iter->sibling) {
+		if ((iter->start >= start + size) || (iter->end <= start))
+			continue;
+
+		__release_region(iter, start, size);
+	}
 	release_mem_region(start, size);
+	up(&hyperv_mmio_lock);
 
 }
 EXPORT_SYMBOL_GPL(vmbus_free_mmio);
Signature · 1 line
1.7.4.1
author
#8 lore raw
Quoted 12 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 3:23 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 5 lines
Quoted 2 lines · K. Y. Srinivasan

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

So these all are for 4.7-rc1?

Jake's PCI driver made it into 4.6 and some of the patches in this series fix issues in the Hyper-V PCI pass-through driver. Is it possible for this series to go into 4.6. If not, 4.7-rc1 is fine.

Regards,

K. Y

#9 lore raw
Quoted 12 lines · KY Srinivasan
Quoted 12 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 3:23 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 8 lines
Quoted 5 lines · K. Y. Srinivasan
Quoted 2 lines

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

So these all are for 4.7-rc1?

Jake's PCI driver made it into 4.6 and some of the patches in this series fix issues in the Hyper-V PCI pass-through driver. Is it possible for this series to go into 4.6. If not, 4.7-rc1 is fine.

Even patch 1? Please be specific where you want patches to be merged to.

greg k-h

author
#10 lore raw
Quoted 30 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 6:48 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 18 lines · KY Srinivasan
Quoted 17 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 3:23 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 2 lines · K. Y. Srinivasan

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

So these all are for 4.7-rc1?

Quoted 7 lines
Quoted 1 line

Jake's PCI driver made it into 4.6 and some of the patches in this series fix

issues in the Hyper-V

Quoted 1 line

PCI pass-through driver. Is it possible for this series to go into 4.6. If not,

4.7-rc1 is fine.

Even patch 1? Please be specific where you want patches to be merged to.

Patch 1 can go into 4.7. If Jake's patches can go into 4.6, that would be good. Do you want me to resend the patches that clearly indicate where the patches need to be merged.

Thank you for your patience.

K. Y

Quoted 2 lines

greg k-h

author
#11 lore raw
Quoted 46 lines

-----Original Message-----
From: KY Srinivasan
Sent: Saturday, April 2, 2016 10:18 PM
To: 'Greg KH' <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: RE: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 33 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 6:48 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 12 lines · KY Srinivasan
Quoted 12 lines

-----Original Message-----
From: Greg KH [mailto:[email protected]]
Sent: Saturday, April 2, 2016 3:23 PM
To: KY Srinivasan <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

Quoted 7 lines
Quoted 5 lines · K. Y. Srinivasan
Quoted 2 lines

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

So these all are for 4.7-rc1?

Jake's PCI driver made it into 4.6 and some of the patches in this series fix

issues in the Hyper-V

Quoted 1 line

PCI pass-through driver. Is it possible for this series to go into 4.6. If not,

4.7-rc1 is fine.

Quoted 7 lines
Quoted 2 lines

Even patch 1? Please be specific where you want patches to be merged to.

Patch 1 can go into 4.7. If Jake's patches can go into 4.6, that would be good. Do you want me
to resend the patches that clearly indicate where the patches need to be merged.

Greg,

Please drop this set. Jake has sent out a new series that we may want to pick up. I will resend the patches I sent the on April 2, 2016 with appropriate adjustments.

Regards,

K. Y

#12 lore raw
In reply to K. Y. Srinivasan
Quoted 10 lines · K. Y. Srinivasan

Cleanup and mmio management. Also included is a patch to fix an issue in KVP.

Jake Oshins (5):
hv: Make a function to free mmio regions through vmbus
hv: Lock access to hyperv_mmio resource tree
hv: Use new vmbus_mmio_free() from client drivers.
hv: Reverse order of resources in hyperv_mmio
hv: Track allocations of children of hv_vmbus in private resource
tree

It seems there is an updated version of the patchset from Jake:
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2016-April/088262.html

It consists of 7 patches. It would probably make sense to take them all I think.

Quoted 11 lines

Vitaly Kuznetsov (1):
Drivers: hv: kvp: fix IP Failover

 drivers/hv/hv_kvp.c             |   31 +++++++++++++++++++++
 drivers/hv/hyperv_vmbus.h       |    5 +++
 drivers/hv/vmbus_drv.c          |   56 ++++++++++++++++++++++++++++++++++-----
 drivers/pci/host/pci-hyperv.c   |   14 +++++-----
 drivers/video/fbdev/hyperv_fb.c |    4 +-
 include/linux/hyperv.h          |    2 +-
 6 files changed, 95 insertions(+), 17 deletions(-)
Signature · 1 line
  Vitaly