From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH 3/5] vDPA: introduce vDPA bus Date: Sun, 19 Jan 2020 04:59:20 -0500 Message-ID: <20200119045849-mutt-send-email-mst@kernel.org> References: <20200116124231.20253-1-jasowang@redhat.com> <20200116124231.20253-4-jasowang@redhat.com> <20200117070324-mutt-send-email-mst@kernel.org> <239b042c-2d9e-0eec-a1ef-b03b7e2c5419@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org To: Shahaf Shuler Cc: Rob Miller , Jason Wang , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "virtualization@lists.linux-foundation.org" , Netdev , "Bie, Tiwei" , Jason Gunthorpe , "maxime.coquelin@redhat.com" , "Liang, Cunming" , "Wang, Zhihong" , "Wang, Xiao W" , "haotian.wang@sifive.com" , "Zhu, Lingshan" , "eperezma@redhat.com" , "lulu@redhat.com" , Parav Pandit List-Id: virtualization@lists.linuxfoundation.org On Sun, Jan 19, 2020 at 09:07:09AM +0000, Shahaf Shuler wrote: > >Technically, we can keep the incremental API > >here and let the vendor vDPA drivers to record the full mapping > >internally which may slightly increase the complexity of vendor driver. > > What will be the trigger for the driver to know it received the last mapping on this series and it can now push it to the on-chip IOMMU? Some kind of invalidate API? -- MST