[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 2/2] VT-d: Fix vt-d flush timeout issue.
> From: Xu, Quan > Sent: Thursday, December 03, 2015 4:09 PM > > If IOTLB/Context/IETC flush is timeout, we should think > all devices under this IOMMU cannot function correctly. > So for each device under this IOMMU we'll mark it as > unassignable and kill the domain owning the device. > > If Device-TLB flush is timeout, we'll mark the target > ATS device as unassignable and kill the domain owning > this device. When the invalidation request descriptor > is timeout, hypervisor cannot find out which Device-TLB > invalidate descriptor submitted before is not correct. > So mark all of the domain's ATS devices as unassignable. Another thought here. If we do timeout check within dev_invalidate_iotlb for each ATS device, could we identify bogus device accurately? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |