Re: [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range

On Wed, Mar 05, 2025 at 03:54:56PM +0100, Jan Beulich wrote: > On 05.03.2025 15:35, Roger Pau Monné wrote: > > On Wed, Mar 05, 2025 at 03:27:18PM +0100, Jan Beulich wrote: > >> On 19.02.2025 17:48, Roger Pau Monne wrote: > >>> Hello, > >>> > >>> First two patches are preparatory changes to reduce t

Re: [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range

On 05.03.2025 15:35, Roger Pau Monné wrote: > On Wed, Mar 05, 2025 at 03:27:18PM +0100, Jan Beulich wrote: >> On 19.02.2025 17:48, Roger Pau Monne wrote: >>> Hello, >>> >>> First two patches are preparatory changes to reduce the changes required >>> in patch 3. I would have wanted those to go in 4

Re: [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range

On Wed, Mar 05, 2025 at 03:27:18PM +0100, Jan Beulich wrote: > On 19.02.2025 17:48, Roger Pau Monne wrote: > > Hello, > > > > First two patches are preparatory changes to reduce the changes required > > in patch 3. I would have wanted those to go in 4.20 to fix the issues > > on Lenovo Thinkpads,

Re: [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range

On 19.02.2025 17:48, Roger Pau Monne wrote: > Hello, > > First two patches are preparatory changes to reduce the changes required > in patch 3. I would have wanted those to go in 4.20 to fix the issues > on Lenovo Thinkpads, but it's too late now. > > Thanks, Roger. > > Roger Pau Monne (3): >

[PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range

Hello, First two patches are preparatory changes to reduce the changes required in patch 3. I would have wanted those to go in 4.20 to fix the issues on Lenovo Thinkpads, but it's too late now. Thanks, Roger. Roger Pau Monne (3): x86/dom0: correctly set the maximum ->iomem_caps bound for PVH