Re: [PATCH v3 2/2] drivers/char: mark extra reserved device memory in memory map

On Wed, Apr 17, 2024 at 04:17:48PM +0200, Jan Beulich wrote: > On 14.04.2024 02:32, Marek Marczykowski-Górecki wrote: > > On Wed, Apr 03, 2024 at 09:10:40AM +0200, Jan Beulich wrote: > >> On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote: > >>> The IOMMU driver checks if RMRR/IVMD are marked

Re: [PATCH v3 2/2] drivers/char: mark extra reserved device memory in memory map

On 14.04.2024 02:32, Marek Marczykowski-Górecki wrote: > On Wed, Apr 03, 2024 at 09:10:40AM +0200, Jan Beulich wrote: >> On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote: >>> The IOMMU driver checks if RMRR/IVMD are marked as reserved in memory >>> map. This should be true for addresses

Re: [PATCH v3 2/2] drivers/char: mark extra reserved device memory in memory map

On Wed, Apr 03, 2024 at 09:10:40AM +0200, Jan Beulich wrote: > On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote: > > The IOMMU driver checks if RMRR/IVMD are marked as reserved in memory > > map. This should be true for addresses coming from the firmware, but > > when extra pages used by Xen

Re: [PATCH v3 2/2] drivers/char: mark extra reserved device memory in memory map

On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote: > The IOMMU driver checks if RMRR/IVMD are marked as reserved in memory > map. This should be true for addresses coming from the firmware, but > when extra pages used by Xen itself are included in the mapping, those > are taken from usable RAM

[PATCH v3 2/2] drivers/char: mark extra reserved device memory in memory map

The IOMMU driver checks if RMRR/IVMD are marked as reserved in memory map. This should be true for addresses coming from the firmware, but when extra pages used by Xen itself are included in the mapping, those are taken from usable RAM used. Mark those pages as reserved too. Not marking the pages