From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v11 5/5] net/virtio: support GUEST ANNOUNCE Date: Fri, 19 Jan 2018 17:33:55 +0000 Message-ID: References: <20180110012356.57456-4-xiao.w.wang@intel.com> <20180116214103.67803-1-xiao.w.wang@intel.com> <20180116214103.67803-6-xiao.w.wang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, thomas@monjalon.net, tiwei.bie@intel.com, stephen@networkplumber.org To: Xiao Wang , yliu@fridaylinux.org, olivier.matz@6wind.com, maxime.coquelin@redhat.com, Thomas Monjalon Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 586B71B03F for ; Fri, 19 Jan 2018 18:33:59 +0100 (CET) In-Reply-To: <20180116214103.67803-6-xiao.w.wang@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/16/2018 9:41 PM, Xiao Wang wrote: > When live migration is done, for the backup VM, either the virtio > frontend or the vhost backend needs to send out gratuitous RARP packet > to announce its new network location. > > This patch enables VIRTIO_NET_F_GUEST_ANNOUNCE feature to support live > migration scenario where the vhost backend doesn't have the ability to > generate RARP packet. > > Brief introduction of the work flow: > 1. QEMU finishes live migration, pokes the backup VM with an interrupt. > 2. Virtio interrupt handler reads out the interrupt status value, and > realizes it needs to send out RARP packet to announce its location. > 3. Pause device to stop worker thread touching the queues. > 4. Inject a RARP packet into a Tx Queue. > 5. Ack the interrupt via control queue. > 6. Resume device to continue packet processing. > > Signed-off-by: Xiao Wang > Reviewed-by: Maxime Coquelin Hi Yuanhan, This commit breaks the build! As far as I understand you send a fix but merged into other patch, which leaves this commit still broken. What do you think sending a fix that can be mergable to this one, so I can squash it on next-net? Thanks, ferruh