On Thu, Nov 20, 2014 at 12:31:48PM +0100, Jan Beulich wrote:
> >>> On 19.11.14 at 20:46, wrote:
> > @@ -237,6 +248,42 @@
> > }
> > }
> >
> > +static void __init parse_snb_timeout(const char *s)
> > +{
> > + int not;
> > +
> > + switch (*s) {
> > +
> > + case '\0':
> > + snb
>>> On 19.11.14 at 20:46, wrote:
> @@ -237,6 +248,42 @@
> }
> }
>
> +static void __init parse_snb_timeout(const char *s)
> +{
> + int not;
> +
> + switch (*s) {
> +
> + case '\0':
> + snb_igd_timeout = SNB_IGD_TIMEOUT_LEGACY;
> + break;
> +
> + case
On Wed, 2014-11-19 at 12:46 -0700, Donald D. Dugger wrote:
> Currently the quirk code for SandyBridge uses the VTd timeout value when
You've got a typo in the subject ("SnadyBridge").
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen
Currently the quirk code for SandyBridge uses the VTd timeout value when
writing to an IGD register. This is the wrong timeout to use and, at
1000 msec., is also much too large. This patch changes the quirk code to
use a timeout that is specific to the IGD device and allows the user
control of th
