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

Re: [Xen-devel] [PATCH V2] Decouple SnadyBridge quirk form VTd timeout

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.

Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786

-----Original Message-----
From: Jan Beulich [mailto:JBeulich@xxxxxxxx] 
Sent: Monday, November 17, 2014 7:41 AM
To: Dugger, Donald D
Cc: Kay, Allen M; Dong, Eddie; Auld, Will; xen-devel@xxxxxxxxxxxxx
Subject: RE: [PATCH V2] Decouple SnadyBridge quirk form VTd timeout

>>> On 17.11.14 at 15:27, <donald.d.dugger@xxxxxxxxx> wrote:
> I'm a big believer in backward compatibility, especially in not doing 
> things that change current defined behavior.  The current 
> `snb_igd_quirk' flag enables the quirk code with a 1sec timeout.  Even 
> though that value is excessive silently changing the meaning of the parameter 
> just seems wrong.

But it's the purpose of the patch to change this.


Xen-devel mailing list



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