All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Huawei Xie <huawei.xie@intel.com>
Cc: dev@dpdk.org, mst@redhat.com
Subject: Re: [PATCH v2] vhost: flush used->idx update before reading avail->flags
Date: Wed, 13 May 2015 12:46:30 +0200	[thread overview]
Message-ID: <1907109.z7RyHoHxuq@xps13> (raw)
In-Reply-To: <1430305884-9139-1-git-send-email-huawei.xie@intel.com>

2015-04-29 19:11, Huawei Xie:
> update of used->idx and read of avail->flags could be reordered.
> memory fence should be used to ensure the order, otherwise guest could see a stale used->idx value after it toggles the interrupt suppression flag.
> After guest sets the interrupt suppression flag, it will check if there is more buffer to process through used->idx. If it sees a stale value, it will exit the processing while host willn't send interrupt to guest.
> 
> Signed-off-by: Huawei Xie <huawei.xie@intel.com>

Applied with following title, thanks
	vhost: fix virtio freeze due to missed interrupt

  reply	other threads:[~2015-05-13 10:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 16:33 [PATCH] vhost: flush used->idx update before reading avail->flags Huawei Xie
     [not found] ` <1429720392-25345-1-git-send-email-huawei.xie-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-04-23 13:57   ` Luke Gorrie
2015-04-24  1:01   ` Linhaifeng
     [not found]     ` <553995DB.4000801-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-24  2:40       ` Xie, Huawei
2015-04-24  7:27       ` Luke Gorrie
2015-06-09  7:04         ` Linhaifeng
2015-06-09  7:45           ` Luke Gorrie
2015-06-09  8:46           ` Michael S. Tsirkin
2015-06-09 13:34             ` Xie, Huawei
2015-06-10  2:36               ` Linhaifeng
2015-06-10  8:30             ` Luke Gorrie
2015-06-11  0:50               ` Linhaifeng
2015-04-29 11:11   ` [PATCH v2] " Huawei Xie
2015-05-13 10:46     ` Thomas Monjalon [this message]
2015-05-15 13:43       ` Nikita Kalyazin
2015-05-15 15:23         ` Michael S. Tsirkin
2015-05-18  6:18           ` Nikita Kalyazin

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=1907109.z7RyHoHxuq@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.