Well, Allen (the original VTd maintainer and the author of the IGD quirk code) agrees that the original IGD quirk timeout code just used the VTd timeout as a convenience. He's the one who identified 670 msec as the theoretical max latency for IGD access but, due to certification issues, suggests we keep the current 1 sec max as a default.
-- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 -----Original Message----- From: Jan Beulich [mailto:jbeul...@suse.com] Sent: Monday, November 17, 2014 7:58 AM To: Dugger, Donald D Cc: Kay, Allen M; Dong, Eddie; Auld, Will; xen-devel@lists.xen.org Subject: RE: [PATCH V2] Decouple SnadyBridge quirk form VTd timeout >>> On 17.11.14 at 15:51, <donald.d.dug...@intel.com> wrote: > My primary goal is to decouple the IGD quirk code from the VTd timeout > value, the two are unrelated and shouldn't be using the same define. > In the process we can clean up the IGD code so that, if a user wants, > the user can specify a more appropriate timeout value for the quirk > code. There's no need to change the current behavior of the flag, just give > the user more options. It the VT-d maintainers agree with that, I certainly won't stand in the way. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
