From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range
Date: Wed, 5 Mar 2025 15:35:21 +0100 [thread overview]
Message-ID: <Z8hhKa-KdTbmp6rE@macbook.local> (raw)
In-Reply-To: <db3113a1-4cae-4d2b-8840-645f56af3c51@suse.com>
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, but it's too late now.
> >
> > Thanks, Roger.
> >
> > Roger Pau Monne (3):
> > x86/dom0: correctly set the maximum ->iomem_caps bound for PVH
> > x86/iommu: account for IOMEM caps when populating dom0 IOMMU
> > page-tables
> > x86/dom0: be less restrictive with the Interrupt Address Range
>
> I'm uncertain whether to take this and "x86/pvh: workaround missing MMIO
> regions in dom0 p2m" for backport. The sole Fixes: tag is in patch 1 here.
> Thoughts?
At least the ones here would be helpful for the reported Lenovo
Thinkpad issue. The PVH p2m addition would be nice IMO.
Thanks, Roger.
next prev parent reply other threads:[~2025-03-05 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:48 [PATCH v3 0/3] x86/dom0: be less restrictive with the Interrupt Address Range Roger Pau Monne
2025-02-19 16:48 ` [PATCH v3 1/3] x86/dom0: correctly set the maximum ->iomem_caps bound for PVH Roger Pau Monne
2025-02-20 8:22 ` Jan Beulich
2025-02-20 8:49 ` Roger Pau Monné
2025-02-20 13:02 ` Jan Beulich
2025-02-19 16:48 ` [PATCH v3 2/3] x86/iommu: account for IOMEM caps when populating dom0 IOMMU page-tables Roger Pau Monne
2025-02-20 8:29 ` Jan Beulich
2025-02-19 16:48 ` [PATCH v3 3/3] x86/dom0: be less restrictive with the Interrupt Address Range Roger Pau Monne
2025-02-20 8:33 ` Jan Beulich
2025-02-20 8:55 ` Roger Pau Monné
2025-02-20 13:30 ` Jan Beulich
2025-02-20 15:40 ` Roger Pau Monné
2025-02-20 16:05 ` Jan Beulich
2025-02-20 16:16 ` Roger Pau Monné
2025-03-05 14:27 ` [PATCH v3 0/3] " Jan Beulich
2025-03-05 14:35 ` Roger Pau Monné [this message]
2025-03-05 14:54 ` Jan Beulich
2025-03-05 17:42 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z8hhKa-KdTbmp6rE@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.