From: Greg KH <greg@kroah.com>
To: Long Li <longli@exchange.microsoft.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hv: retry infinitely on hypercall transient failures
Date: Thu, 5 Jan 2017 08:47:42 +0100 [thread overview]
Message-ID: <20170105074742.GB4547@kroah.com> (raw)
In-Reply-To: <1483582340-26770-1-git-send-email-longli@exchange.microsoft.com>
On Wed, Jan 04, 2017 at 06:12:20PM -0800, Long Li wrote:
> 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.
Again, never retry "forever", always have a way out, otherwise you will
crash.
And again, why are you making this change? What problem does it solve?
greg k-h
next prev parent reply other threads:[~2017-01-05 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 2:12 [PATCH v2] hv: retry infinitely on hypercall transient failures Long Li
2017-01-05 7:47 ` Greg KH [this message]
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=20170105074742.GB4547@kroah.com \
--to=greg@kroah.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@exchange.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