From: Jason Wang <jasowang@redhat.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org, olaf@aepfle.de,
apw@canonical.com, kys@microsoft.com, vkuznets@redhat.com,
haiyangz@microsoft.com
Subject: Re: [PATCH v2 2/3] hv: vmbus_post_msg: retry the hypercall on some transient errors
Date: Mon, 02 Feb 2015 09:49:16 +0008 [thread overview]
Message-ID: <1422870076.7028.6@smtp.corp.redhat.com> (raw)
In-Reply-To: <1422851763-2391-1-git-send-email-decui@microsoft.com>
On Mon, Feb 2, 2015 at 12:36 PM, Dexuan Cui <decui@microsoft.com> wrote:
> I got HV_STATUS_INVALID_CONNECTION_ID on Hyper-V 2008 R2 when keeping
> running
> "rmmod hv_netvsc; modprobe hv_netvsc; rmmod hv_utils; modprobe
> hv_utils"
> in a Linux guest. Looks the host has some kind of throttling
> mechanism if
> some kinds of hypercalls are sent too frequently.
Better to clarify this kind of throttling. Looks like it only affects
HVCALL_POST_MESSAGE. Other looks good.
Reviewed-by: Jason Wang <jasowang@redhat.com>
>
> Without the patch, the driver can occasionally fail to load.
>
> Also let's retry HV_STATUS_INSUFFICIENT_MEMORY, though we didn't get
> it
> before.
>
> Removed 'case -ENOMEM', since the hypervisor doesn't return this.
>
> CC: "K. Y. Srinivasan" <kys@microsoft.com>
> Signed-off-by: Dexuan Cui <decui@microsoft.com>
> ---
>
> v2:
> updated the subject and changelog
> on HV_STATUS_INVALID_CONNECTION_ID: ret = -EAGAIN;
> added HV_STATUS_INSUFFICIENT_MEMORY
> removed unreachable -ENOMEM
> changed the delay from 100ms to 1000ms
>
> arch/x86/include/uapi/asm/hyperv.h | 2 ++
> drivers/hv/connection.c | 11 +++++++++--
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/uapi/asm/hyperv.h
> b/arch/x86/include/uapi/asm/hyperv.h
> index 90c458e..ce6068d 100644
> --- a/arch/x86/include/uapi/asm/hyperv.h
> +++ b/arch/x86/include/uapi/asm/hyperv.h
> @@ -225,6 +225,8 @@
> #define HV_STATUS_INVALID_HYPERCALL_CODE 2
> #define HV_STATUS_INVALID_HYPERCALL_INPUT 3
> #define HV_STATUS_INVALID_ALIGNMENT 4
> +#define HV_STATUS_INSUFFICIENT_MEMORY 11
> +#define HV_STATUS_INVALID_CONNECTION_ID 18
> #define HV_STATUS_INSUFFICIENT_BUFFERS 19
>
> typedef struct _HV_REFERENCE_TSC_PAGE {
> diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
> index c4acd1c..af2388f 100644
> --- a/drivers/hv/connection.c
> +++ b/drivers/hv/connection.c
> @@ -440,9 +440,16 @@ int vmbus_post_msg(void *buffer, size_t buflen)
> ret = hv_post_message(conn_id, 1, buffer, buflen);
>
> switch (ret) {
> + 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;
> - case -ENOMEM:
> break;
> case HV_STATUS_SUCCESS:
> return ret;
> @@ -452,7 +459,7 @@ int vmbus_post_msg(void *buffer, size_t buflen)
> }
>
> retries++;
> - msleep(100);
> + msleep(1000);
> }
> return ret;
> }
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-02-02 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 4:36 Dexuan Cui
2015-02-02 9:41 ` Jason Wang [this message]
2015-02-02 10:13 ` Dexuan Cui
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=1422870076.7028.6@smtp.corp.redhat.com \
--to=jasowang@redhat.com \
--cc=apw@canonical.com \
--cc=decui@microsoft.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--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
Powered by JetHome