[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 1/2] x86/iommu: fix wrong usage of iommu_hwdom_inclusive

To: "Roger Pau Monne" <roger.pau@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 02 Oct 2018 02:36:20 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 02 Oct 2018 08:36:31 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

>>> On 02.10.18 at 10:08, <roger.pau@xxxxxxxxxx> wrote:
> iommu_hwdom_inclusive was used where iommu_hwdom_reserved should be
> used.
> 
> Reported-by: Suravee Suthikulpanit <suravee.suthikulpanit@xxxxxxx>
> Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

References:
- [Xen-devel] [PATCH v2 1/2] x86/iommu: fix wrong usage of iommu_hwdom_inclusive
  - From: Roger Pau Monne

Prev by Date: [Xen-devel] Question, How to share interrupt between Doms
Next by Date: Re: [Xen-devel] [xen-unstable test] 128240: regressions - FAIL
Previous by thread: Re: [Xen-devel] [PATCH v2 2/2] amd/iommu: remove hidden AMD inclusive mappings
Next by thread: [Xen-devel] Question, How to share interrupt between Doms
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.