Re: [PATCH v3 05/11] hw/arm/smmu-common: Manage IOTLB block entries

2020-07-10 Thread Peter Maydell
On Wed, 8 Jul 2020 at 15:19, Eric Auger wrote: > > At the moment each entry in the IOTLB corresponds to a page sized > mapping (4K, 16K or 64K), even if the page belongs to a mapped > block. In case of block mapping this unefficiently consumes IOTLB > entries. > > Change the value of the entry so

Re: [PATCH v3 05/11] hw/arm/smmu-common: Manage IOTLB block entries

2020-07-10 Thread Peter Maydell
On Wed, 8 Jul 2020 at 15:19, Eric Auger wrote: > > At the moment each entry in the IOTLB corresponds to a page sized > mapping (4K, 16K or 64K), even if the page belongs to a mapped > block. In case of block mapping this unefficiently consumes IOTLB > entries. > > Change the value of the entry so

[PATCH v3 05/11] hw/arm/smmu-common: Manage IOTLB block entries

2020-07-08 Thread Eric Auger
At the moment each entry in the IOTLB corresponds to a page sized mapping (4K, 16K or 64K), even if the page belongs to a mapped block. In case of block mapping this unefficiently consumes IOTLB entries. Change the value of the entry so that it reflects the actual mapping it belongs to (block or p