>>> On 02.11.15 at 09:03, <kevin.t...@intel.com> wrote: > Based on above information, we propose to continue spin-timeout > model w/ some adjustment, which fixes current timeout concern > and also allows limited ATS support in a light way: > > 1) reduce spin timeout to 1ms, which can be boot-time changed > up to 10ms. > > 2) if timeout expires, kill the VM which the target device is assigned > to. Optionally hypervisor may mark device non-assignable. > > It works for devices w/o ATS. It works for integrated devices w/ ATS. > It might or might not work for discrete devices w/ ATS, but we can > re-evaluate the gain vs. software complexity of async flush until we > see many discrete devices breaking the timeout assumptions in the > future. > > Thoughts?
Yes, let's take this approach as a first step at least. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
