> -----Original Message----- > From: Wei Liu [mailto:[email protected]] > Sent: 16 July 2018 15:14 > To: Paul Durrant <[email protected]> > Cc: [email protected]; Andrew Cooper > <[email protected]>; George Dunlap > <[email protected]>; Ian Jackson <[email protected]>; Jan > Beulich <[email protected]>; Konrad Rzeszutek Wilk > <[email protected]>; Stefano Stabellini <[email protected]>; Tim > (Xen.org) <[email protected]>; Wei Liu <[email protected]>; Daniel De Graaf > <[email protected]> > Subject: Re: [PATCH v2 06/13] public / x86: introduce > __HYPERCALL_iommu_op > > On Sat, Jul 07, 2018 at 12:05:19PM +0100, Paul Durrant wrote: > > This patch introduces the boilerplate for a new hypercall to allow a > > domain to control IOMMU mappings for its own pages. > > Whilst there is duplication of code between the native and compat entry > > points which appears ripe for some form of combination, I think it is > > better to maintain the separation as-is because the compat entry point > > will necessarily gain complexity in subsequent patches. > > > > Since this is a new op, why is there compatibility issue? Can we do away > with the compat entry point all together? > > I haven't read the rest of this series, maybe it will become clearer > later.
Look at the patch adding the query op... that's when it becomes necessary. Paul > > Wei. _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
