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, haiyangz@microsoft.com
Subject: Re: [PATCH 2/3] hv: vmbus_post_msg: retry the hypercall on HV_STATUS_INVALID_CONNECTION_ID
Date: Fri, 30 Jan 2015 02:55:10 +0008 [thread overview]
Message-ID: <1422586030.5014.1@smtp.corp.redhat.com> (raw)
In-Reply-To: <1422529361-28228-1-git-send-email-decui@microsoft.com>
On Thu, Jan 29, 2015 at 7:02 PM, Dexuan Cui <decui@microsoft.com> wrote:
> I got the hypercall error code on Hyper-V 2008 R2 when keeping running
> "rmmod hv_netvsc; modprobe hv_netvsc; rmmod hv_utils; modprobe
> hv_utils"
> in a Linux guest.
>
> Without the patch, the driver can occasionally fail to load.
>
> CC: "K. Y. Srinivasan" <kys@microsoft.com>
> Signed-off-by: Dexuan Cui <decui@microsoft.com>
> ---
> arch/x86/include/uapi/asm/hyperv.h | 1 +
> drivers/hv/connection.c | 9 +++++++++
> 2 files changed, 10 insertions(+)
>
> diff --git a/arch/x86/include/uapi/asm/hyperv.h
> b/arch/x86/include/uapi/asm/hyperv.h
> index 90c458e..b9daffb 100644
> --- a/arch/x86/include/uapi/asm/hyperv.h
> +++ b/arch/x86/include/uapi/asm/hyperv.h
> @@ -225,6 +225,7 @@
> #define HV_STATUS_INVALID_HYPERCALL_CODE 2
> #define HV_STATUS_INVALID_HYPERCALL_INPUT 3
> #define HV_STATUS_INVALID_ALIGNMENT 4
> +#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..8bd05f3 100644
> --- a/drivers/hv/connection.c
> +++ b/drivers/hv/connection.c
> @@ -440,6 +440,15 @@ 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 or the host is under low resource
> + * conditions: let's wait 1 more second before
> + * retrying the hypercall.
> + */
The name HV_STATUS_INVALID_CONNECTION_ID is really confusing in this
case. Since it does not show any meaning of lacking resources.
> + msleep(1000);
> + break;
> case HV_STATUS_INSUFFICIENT_BUFFERS:
> ret = -ENOMEM;
I thought host should return this error value when lacking resources?
>
> case -ENOMEM:
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-01-30 2:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 11:02 [PATCH 2/3] hv: vmbus_post_msg: retry the hypercall on HV_STATUS_INVALID_CONNECTION_ID Dexuan Cui
2015-01-29 13:30 ` Vitaly Kuznetsov
2015-01-30 5:30 ` Dexuan Cui
2015-01-30 17:29 ` Vitaly Kuznetsov
2015-02-01 3:37 ` Dexuan Cui
2015-02-01 19:48 ` KY Srinivasan
2015-01-30 2:47 ` Jason Wang [this message]
2015-01-30 5:34 ` 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=1422586030.5014.1@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 \
/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