From: Long Li <longli@exchange.microsoft.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
Long Li <longli@microsoft.com>
Subject: [PATCH v2] hv: retry infinitely on hypercall transient failures
Date: Wed, 4 Jan 2017 18:12:20 -0800 [thread overview]
Message-ID: <1483582340-26770-1-git-send-email-longli@exchange.microsoft.com> (raw)
From: Long Li <longli@microsoft.com>
Hyper-v host guarantees that a hypercall will finish in reasonable time.
Retry infinitely on transient failures to avoid returning error to upper layer.
Signed-off-by: Long Li <longli@microsoft.com>
---
drivers/hv/connection.c | 30 ++++++++++++++----------------
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
index 6ce8b87..4b3cfde 100644
--- a/drivers/hv/connection.c
+++ b/drivers/hv/connection.c
@@ -438,46 +438,44 @@ void vmbus_on_event(unsigned long data)
int vmbus_post_msg(void *buffer, size_t buflen)
{
union hv_connection_id conn_id;
- int ret = 0;
- int retries = 0;
+ int ret;
u32 usec = 1;
conn_id.asu32 = 0;
conn_id.u.id = VMBUS_MESSAGE_CONNECTION_ID;
/*
- * hv_post_message() can have transient failures because of
- * insufficient resources. Retry the operation a couple of
- * times before giving up.
+ * hv_post_message() can have transient failures. We retry infinitely
+ * on these failures because host guarantees hypercall will finish.
*/
- while (retries < 20) {
+ while (1) {
ret = hv_post_message(conn_id, 1, buffer, buflen);
switch (ret) {
+ /*
+ * Retry on transient failures:
+ * 1. HV_STATUS_INVALID_CONNECTION_ID:
+ * We send messages too frequently.
+ *
+ * 2. HV_STATUS_INSUFFICIENT_MEMORY and
+ * HV_STATUS_INSUFFICIENT_BUFFERS:
+ * The host is temporariliy running out of resources.
+ */
case HV_STATUS_INVALID_CONNECTION_ID:
- /*
- * We could get this if we send messages too
- * frequently.
- */
- ret = -EAGAIN;
- break;
case HV_STATUS_INSUFFICIENT_MEMORY:
case HV_STATUS_INSUFFICIENT_BUFFERS:
- ret = -ENOMEM;
break;
case HV_STATUS_SUCCESS:
- return ret;
+ return 0;
default:
pr_err("hv_post_msg() failed; error code:%d\n", ret);
return -EINVAL;
}
- retries++;
udelay(usec);
if (usec < 2048)
usec *= 2;
}
- return ret;
}
/*
--
2.7.4
next reply other threads:[~2017-01-05 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 2:12 Long Li [this message]
2017-01-05 7:47 ` [PATCH v2] hv: retry infinitely on hypercall transient failures Greg KH
2017-01-07 7:23 ` Long Li
2017-01-07 7:42 ` Greg KH
2017-01-07 8:06 ` Long Li
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=1483582340-26770-1-git-send-email-longli@exchange.microsoft.com \
--to=longli@exchange.microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.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