From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-3891-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [66.179.20.138]) by lists.oasis-open.org (Postfix) with ESMTP id 8E69D58191A0 for ; Thu, 19 Apr 2018 10:00:47 -0700 (PDT) Date: Thu, 19 Apr 2018 20:00:34 +0300 From: "Michael S. Tsirkin" Message-ID: <20180419195651-mutt-send-email-mst@kernel.org> References: <20180412151232.17506-1-tiwei.bie@intel.com> <20180412151232.17506-7-tiwei.bie@intel.com> <20180418192154-mutt-send-email-mst@kernel.org> <20180419111439.i6gfhnept6wy7uzp@debian> <20180419182035-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [virtio-dev] Re: [PATCH v3 6/6] vhost-user: support registering external host notifiers To: "Liang, Cunming" Cc: Paolo Bonzini , "Bie, Tiwei" , "jasowang@redhat.com" , "alex.williamson@redhat.com" , "stefanha@redhat.com" , "qemu-devel@nongnu.org" , "virtio-dev@lists.oasis-open.org" , "Daly, Dan" , "Tan, Jianfeng" , "Wang, Zhihong" , "Wang, Xiao W" List-ID: On Thu, Apr 19, 2018 at 04:52:20PM +0000, Liang, Cunming wrote: > > > > -----Original Message----- > > From: Paolo Bonzini [mailto:pbonzini@redhat.com] > > Sent: Thursday, April 19, 2018 11:52 PM > > To: Michael S. Tsirkin ; Liang, Cunming > > > > Cc: Bie, Tiwei ; jasowang@redhat.com; > > alex.williamson@redhat.com; stefanha@redhat.com; qemu-devel@nongnu.org; > > virtio-dev@lists.oasis-open.org; Daly, Dan ; Tan, Jianfeng > > ; Wang, Zhihong ; Wang, > > Xiao W > > Subject: Re: [PATCH v3 6/6] vhost-user: support registering external host > > notifiers > > > > On 19/04/2018 17:42, Michael S. Tsirkin wrote: > > >> A compiler barrier is enough on strongly-ordered memory platform. > > >> As it doesn't re-order store, PCI device won't see a stale index > > >> value. But a weakly-ordered memory needs sfence. > > > > > > Oh you are right. > > > > > > So it's only needed for non-intel platforms or when packets are in WC > > > memory then. And I don't know whether dpdk ever puts packets in WC > > > memory. > > > > > > I guess we'll cross this bridge when we get to it. > > > > Non-TSO architectures seem important... > > I'm not familiar with Non-TSO, trying to understand the difference > according to the feature set. Let's say non-TSO architectures do not > set 'weak_barriers'. Then mandatory barrier is used for software. HW > offload on that platform would choose different feature set against > software? Right. We'll need a flag for this feature for starters. It doesn't exist :) Paolo also points out that we should then add code to disallow migration between setups with and without the feature. > If it's not, essentially we're worried about live migration from a TSO to a non-TSO architectures platform? Probably not. > > > > Paolo --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org