Re: [PATCH 4/4] iommu/x86: make unity range checking more strict

2024-02-07 Thread Jan Beulich
On 07.02.2024 10:14, Roger Pau Monné wrote: > On Tue, Feb 06, 2024 at 12:49:08PM +0100, Jan Beulich wrote: >> On 01.02.2024 18:01, Roger Pau Monne wrote: >>> Currently when a unity range overlaps with memory being used as RAM by the >>> hypervisor the result would be that the IOMMU gets disabled.

Re: [PATCH 4/4] iommu/x86: make unity range checking more strict

2024-02-07 Thread Roger Pau Monné
On Tue, Feb 06, 2024 at 12:49:08PM +0100, Jan Beulich wrote: > On 01.02.2024 18:01, Roger Pau Monne wrote: > > Currently when a unity range overlaps with memory being used as RAM by the > > hypervisor the result would be that the IOMMU gets disabled. However that's > > not enough, as even with

Re: [PATCH 4/4] iommu/x86: make unity range checking more strict

2024-02-06 Thread Jan Beulich
On 01.02.2024 18:01, Roger Pau Monne wrote: > Currently when a unity range overlaps with memory being used as RAM by the > hypervisor the result would be that the IOMMU gets disabled. However that's > not enough, as even with the IOMMU disabled the device will still access the > affected RAM

[PATCH 4/4] iommu/x86: make unity range checking more strict

2024-02-01 Thread Roger Pau Monne
Currently when a unity range overlaps with memory being used as RAM by the hypervisor the result would be that the IOMMU gets disabled. However that's not enough, as even with the IOMMU disabled the device will still access the affected RAM areas. Note that IVMD or RMRR ranges being placed over