Re: [PATCH v3 1/3] x86/dom0: correctly set the maximum ->iomem_caps bound for PVH

2025-02-20 Thread Jan Beulich
On 20.02.2025 09:49, Roger Pau Monné wrote: > On Thu, Feb 20, 2025 at 09:22:40AM +0100, Jan Beulich wrote: >> On 19.02.2025 17:48, Roger Pau Monne wrote: >>> The logic in dom0_setup_permissions() sets the maximum bound in >>> ->iomem_caps unconditionally using paddr_bits, which is not correct for H

Re: [PATCH v3 1/3] x86/dom0: correctly set the maximum ->iomem_caps bound for PVH

2025-02-20 Thread Roger Pau Monné
On Thu, Feb 20, 2025 at 09:22:40AM +0100, Jan Beulich wrote: > On 19.02.2025 17:48, Roger Pau Monne wrote: > > The logic in dom0_setup_permissions() sets the maximum bound in > > ->iomem_caps unconditionally using paddr_bits, which is not correct for HVM > > based domains. Instead use domain_max_p

Re: [PATCH v3 1/3] x86/dom0: correctly set the maximum ->iomem_caps bound for PVH

2025-02-20 Thread Jan Beulich
On 19.02.2025 17:48, Roger Pau Monne wrote: > The logic in dom0_setup_permissions() sets the maximum bound in > ->iomem_caps unconditionally using paddr_bits, which is not correct for HVM > based domains. Instead use domain_max_paddr_bits() to get the correct > maximum paddr bits for each possible

[PATCH v3 1/3] x86/dom0: correctly set the maximum ->iomem_caps bound for PVH

2025-02-19 Thread Roger Pau Monne
The logic in dom0_setup_permissions() sets the maximum bound in ->iomem_caps unconditionally using paddr_bits, which is not correct for HVM based domains. Instead use domain_max_paddr_bits() to get the correct maximum paddr bits for each possible domain type. Switch to using PFN_DOWN() instead of