>>> On 23.08.17 at 17:56, wrote:
> On 08/22/2017 04:18 AM, Jan Beulich wrote:
> On 18.08.17 at 23:55, wrote:
>>> On 08/18/2017 05:02 PM, christopher.w.cl...@gmail.com wrote:
From: Christopher Clark
On 08/22/2017 04:18 AM, Jan Beulich wrote:
On 18.08.17 at 23:55, wrote:
On 08/18/2017 05:02 PM, christopher.w.cl...@gmail.com wrote:
From: Christopher Clark
Isolation of devices passed through to domains usually requires an
active
I did test and review this submission back when I worked on the OpenXT
project with Christopher so I can add a reviewed by.
Reviewed-by: Ross Philipson
On Tue, Aug 22, 2017 at 4:18 AM, Jan Beulich wrote:
> >>> On 18.08.17 at 23:55,
>>> On 18.08.17 at 23:55, wrote:
> On 08/18/2017 05:02 PM, christopher.w.cl...@gmail.com wrote:
>> From: Christopher Clark
>>
>> Isolation of devices passed through to domains usually requires an
>> active IOMMU. The existing method of
On 08/18/2017 05:02 PM, christopher.w.cl...@gmail.com wrote:
From: Christopher Clark
Isolation of devices passed through to domains usually requires an
active IOMMU. The existing method of requiring an IOMMU is via a Xen
boot parameter ("iommu=force") which
From: Christopher Clark
Isolation of devices passed through to domains usually requires an
active IOMMU. The existing method of requiring an IOMMU is via a Xen
boot parameter ("iommu=force") which will abort boot if an IOMMU is not
available.
More graceful