linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kelley <mikelley@microsoft.com>
To: Vineeth Pillai <viremana@linux.microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>
Cc: KY Srinivasan <kys@microsoft.com>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] hv_utils: drain the timesync packets on onchannelcallback
Date: Thu, 20 Aug 2020 18:31:12 +0000	[thread overview]
Message-ID: <MW2PR2101MB1052254C5ED7C587E548DB3AD75A0@MW2PR2101MB1052.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20200819174740.47291-1-viremana@linux.microsoft.com>

From: Vineeth Pillai <viremana@linux.microsoft.com> Sent: Wednesday, August 19, 2020 10:48 AM
> 
> There could be instances where a system stall prevents the timesync
> packaets to be consumed. And this might lead to more than one packet
> pending in the ring buffer. Current code empties one packet per callback
> and it might be a stale one. So drain all the packets from ring buffer
> on each callback.
> 
> Signed-off-by: Vineeth Pillai <viremana@linux.microsoft.com>
> ---
>  drivers/hv/hv_util.c | 19 ++++++++++++++++---
>  1 file changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
> index 1357861fd8ae..c0491b727fd5 100644
> --- a/drivers/hv/hv_util.c
> +++ b/drivers/hv/hv_util.c
> @@ -387,10 +387,23 @@ static void timesync_onchannelcallback(void *context)
>  	struct ictimesync_ref_data *refdata;
>  	u8 *time_txf_buf = util_timesynch.recv_buffer;
> 
> -	vmbus_recvpacket(channel, time_txf_buf,
> -			 HV_HYP_PAGE_SIZE, &recvlen, &requestid);
> +	/*
> +	 * Drain the ring buffer and use the last packet to update
> +	 * host_ts
> +	 */
> +	while (1) {
> +		int ret = vmbus_recvpacket(channel, time_txf_buf,
> +					   HV_HYP_PAGE_SIZE, &recvlen,
> +					   &requestid);
> +		if (ret) {
> +			pr_warn("TimeSync IC pkt recv failed (Err: %d)\n",
> +				ret);

Let's use pr_warn_once().

If there's a packet at the head of the ring buffer that specifies a bogus length,
we could take the error path.  But the bad packet stays at the head of the ring buffer,
so if we end up back here again, we'll spit out the same error message.  We
actually should not end up here again because Hyper-V shouldn't interrupt
when adding a packet to a non-empty ring buffer, but who knows what might
happen.

> +			break;
> +		}
> +
> +		if (!recvlen)
> +			break;
> 
> -	if (recvlen > 0) {
>  		icmsghdrp = (struct icmsg_hdr *)&time_txf_buf[
>  				sizeof(struct vmbuspipe_hdr)];
> 
> --
> 2.17.1


  reply	other threads:[~2020-08-20 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 17:47 [PATCH] hv_utils: drain the timesync packets on onchannelcallback Vineeth Pillai
2020-08-20 18:31 ` Michael Kelley [this message]
2020-08-20 21:48   ` Vineeth Pillai

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=MW2PR2101MB1052254C5ED7C587E548DB3AD75A0@MW2PR2101MB1052.namprd21.prod.outlook.com \
    --to=mikelley@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthemmin@microsoft.com \
    --cc=viremana@linux.microsoft.com \
    --cc=wei.liu@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).