This patch adds an iommu_op which checks whether it is possible or
safe for a domain to modify its own IOMMU mappings and, if so, creates
a rangeset to track modifications.
The op passes back a capabilities mask. There is only one bit currently
defined for this mask: XEN_IOMMU_CAP_per_device_mappi
>>> On 23.08.18 at 11:47, wrote:
> This patch adds an iommu_op which checks whether it is possible or
> safe for a domain to modify its own IOMMU mappings and, if so, creates
> a rangeset to track modifications.
Now this can surely grow pretty big?
> --- a/xen/common/iommu_op.c
> +++ b/xen/commo
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 11 September 2018 15:48
> To: Paul Durrant
> Cc: Julien Grall ; Andrew Cooper
> ; Wei Liu ; George
> Dunlap ; Ian Jackson ;
> Stefano Stabellini ; xen-devel de...@lists.xenproject.org>; Konrad Rzeszutek Wilk
> ; T
>>> On 11.09.18 at 17:52, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: 11 September 2018 15:48
>>
>> >>> On 23.08.18 at 11:47, wrote:
>> > This patch adds an iommu_op which checks whether it is possible or
>> > safe for a domain to modify its own IOMMU mappings and, if so, cre
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 12 September 2018 07:54
> To: Paul Durrant
> Cc: Julien Grall ; Andrew Cooper
> ; George Dunlap
> ; Ian Jackson ; Wei Liu
> ; Stefano Stabellini ; xen-
> devel ; Konrad Rzeszutek Wilk
> ; Tim (Xen.org)
> Subject:
