Re: [PATCH v4 3/8] iommu/vt-d: Duplicate iommu_resv_region objects per device list

2019-05-28 Thread Auger Eric
Hi Joerg, On 5/27/19 5:23 PM, Joerg Roedel wrote: > On Mon, May 27, 2019 at 10:55:36AM +0200, Eric Auger wrote: >> -list_add_tail(>resv->list, head); >> +length = rmrr->end_address - rmrr->base_address + 1; >> +resv =

Re: [PATCH v4 3/8] iommu/vt-d: Duplicate iommu_resv_region objects per device list

2019-05-27 Thread Joerg Roedel
On Mon, May 27, 2019 at 10:55:36AM +0200, Eric Auger wrote: > - list_add_tail(>resv->list, head); > + length = rmrr->end_address - rmrr->base_address + 1; > + resv = iommu_alloc_resv_region(rmrr->base_address, > +

[PATCH v4 3/8] iommu/vt-d: Duplicate iommu_resv_region objects per device list

2019-05-27 Thread Eric Auger
intel_iommu_get_resv_regions() aims to return the list of reserved regions accessible by a given @device. However several devices can access the same reserved memory region and when building the list it is not safe to use a single iommu_resv_region object, whose container is the RMRR. This