From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/2] iommu/vt-d: switch to common RMRR checker
Date: Mon, 12 Feb 2024 15:38:07 +0100 [thread overview]
Message-ID: <c27c76ec-36cd-43cb-b76f-e8f95fb27ed8@suse.com> (raw)
In-Reply-To: <20240207153417.89975-3-roger.pau@citrix.com>
On 07.02.2024 16:34, Roger Pau Monne wrote:
> Use the newly introduced generic unity map checker.
>
> Also drop the message recommending the usage of iommu_inclusive_mapping: the
> ranges would end up being mapped anyway even if some of the checks above
> failed, regardless of whether iommu_inclusive_mapping is set. Plus such option
> is not supported for PVH, and it's deprecated.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2024-02-12 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 15:34 [PATCH v2 0/2] iommu/x86: unify RMRR/IVMD range checks Roger Pau Monne
2024-02-07 15:34 ` [PATCH v2 1/2] iommu/x86: introduce a generic IVMD/RMRR range validity helper Roger Pau Monne
2024-02-12 14:34 ` Jan Beulich
2024-02-13 8:11 ` Roger Pau Monné
2024-02-07 15:34 ` [PATCH v2 2/2] iommu/vt-d: switch to common RMRR checker Roger Pau Monne
2024-02-12 14:38 ` Jan Beulich [this message]
2024-02-13 22:37 ` [regression] " Andrew Cooper
2024-02-14 7:45 ` Jan Beulich
2024-02-14 8:45 ` Roger Pau Monné
2024-02-14 9:00 ` Andrew Cooper
2024-02-14 9:24 ` Roger Pau Monné
2024-02-14 9:01 ` Jan Beulich
2024-02-14 9:15 ` Roger Pau Monné
2024-02-14 10:11 ` Andrew Cooper
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=c27c76ec-36cd-43cb-b76f-e8f95fb27ed8@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.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.