[Top] [All Lists]

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

Re: [Xen-devel] [PATCH v2] IOMMU: Prevent VT-d device IOTLB operations on wrong IOMMU

To: "Malcolm Crossley" <malcolm.crossley@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 17 Jun 2014 15:09:11 +0100
Cc: andrew.cooper3@xxxxxxxxxx, kevin.tian@xxxxxxxxx, Aravind.Gopalakrishnan@xxxxxxx, suravee.suthikulpanit@xxxxxxx, xen-devel@xxxxxxxxxxxxx
Delivery-date: Tue, 17 Jun 2014 14:09:27 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 17.06.14 at 15:56, <malcolm.crossley@xxxxxxxxxx> wrote:
> So do I drop the optimisation to avoid the problems with using the const?

I'd prefer if you did so, but the ultimate decision would be with the
AMD maintainers.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v2] IOMMU: Prevent VT-d device IOTLB operations on wrong IOMMU
  - From: Malcolm Crossley
- Re: [Xen-devel] [PATCH v2] IOMMU: Prevent VT-d device IOTLB operations on wrong IOMMU
  - From: Jan Beulich
- Re: [Xen-devel] [PATCH v2] IOMMU: Prevent VT-d device IOTLB operations on wrong IOMMU
  - From: Malcolm Crossley

Prev by Date: Re: [Xen-devel] Xen Security Advisory 99 - unexpected pitfall in xenaccess API
Next by Date: Re: [Xen-devel] pvops upstream status
Previous by thread: Re: [Xen-devel] [PATCH v2] IOMMU: Prevent VT-d device IOTLB operations on wrong IOMMU
Index(es):
- Date
- Thread

Rackspace

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