On Tue, 28 Aug 2018 10:34:19 +0200 Auger Eric <eric.au...@redhat.com> wrote:
> > Anyway, for the new VT-d 3.0 spec. we no longer need this API. In > > stead, I will introduce bind_guest_pasid() API, where per device > > PASID table is allocated by the host. > > So what is the exact state of this series? Is it outdated as you don't > target VT-d 2.5 anymore? Will you keep the rest of the API? Hi Eric, I am not targeting VT-d 2.5 for SVA related work. I am working on the rest of the APIs for supporting VT-d v3, which includes guest PASID bind, fault reporting, and invalidation passdown from the guest. These are based on some recent patches from Baolu. https://lkml.org/lkml/2018/7/16/62 So I feel it is better for you to take over bind_pasid_table() API in your series. I will drop it from my next version. Thanks, Jacob _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu