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

Re: [Xen-devel] [PATCH v4 0/3] VT-d Device-TLB flush issue

>>> Quan Xu <quan.xu@xxxxxxxxx> 12/23/15 9:26 AM >>>
>This patches are based on Kevin Tian's previous discussion 'Revisit VT-d 
>asynchronous flush issue'.
>Fix current timeout concern and also allow limited ATS support in a light way:
>1. Check VT-d Device-TLB flush error.
>This patch checks all kinds of error and all the way up the call trees of VT-d 
>Device-TLB flush.
>2. Reduce spin timeout to 1ms, which can be boot-time changed with 
>For example:
>multiboot /boot/xen.gz ats=1 iommu_qi_timeout_ms=100
>3. Fix vt-d Device-TLB flush timeout issue.
>Now if IOTLB/Context/IETC flush is timeout, panic hypervisor. The coming patch
>set will fix it.

There must have been a misunderstanding: Your earlier outline didn't indicate 
mean to introduce panics here, even if only temporarily. I'm afraid I'm not 
willing to take any conceptually wrong patches anymore with just the promise of
fixing the issue(s) later (and I think we've mentioned this in some past 
on the list, albeit unlikely in the context of any of your work). This may mean 
the earlier described ordering of things you mean to do needs changing.

I'm sorry that you're hit first by this, the more that it was not you but 
colleagues of
yours causing this change to the acceptance model.


Xen-devel mailing list



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