[Xen-devel] RE: Resend: RE: enable_ats_device() call site

["Kay, Allen M" <allen.m.kay@xxxxxxxxx>]

>And why is it VT-d specific then? The problem to solve is that enabling
>may not happen when it is first attempted, in the case where Xen on its
>own can't be certain that using MMCFG is safe. Hence when the device
>gets reported by Dom0 (or when MMCFG gets enabled for the respective
>bus), another attempt needs to be made at enabling it. De-assigning and
>then re-assigning the device to Dom0 seems to be overkill to me.

The part that is VT-d specific is ATS capability reporting in ACPI DMAR
table for reporting ATS capability in root ports.  I not so clear on what
do you mean by making another attempt when initial ATS enabling attempt fails.
Do you have a patch to address this issue?

Allen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel