From: "Tian, Kevin" <kevin.tian@intel.com>
To: Ting-Wei Lan <lantw44@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
Julien Grall <julien.grall@citrix.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v4] VT-d: add iommu=igfx option to workaround graphics issues
Date: Thu, 6 Aug 2015 00:49:51 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D142ABF266@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1438794606-6891-1-git-send-email-lantw44@gmail.com>
> From: Ting-Wei Lan [mailto:lantw44@gmail.com]
> Sent: Thursday, August 06, 2015 1:10 AM
>
> When using Linux >= 3.19 (commit 47591df) as dom0 on some Intel Ironlake
> devices, It is possible to encounter graphics issues that make screen
> unreadable or crash the system. It was reported in freedesktop bugzilla:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=90037
>
> As we still cannot find a proper fix for this problem, this patch adds
> iommu=igfx option to control whether Intel graphics IOMMU is enabled.
> Running Xen with iommu=no-igfx is similar to running Linux with
> intel_iommu=igfx_off, which disables IOMMU for Intel GPU. This can be
> used by users to manually workaround the problem before a fix is
> available for i915 driver.
>
> Signed-off-by: Ting-Wei Lan <lantw44@gmail.com>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Release-acked-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: Kevin Tian <kevin.tian@intel.com>
next prev parent reply other threads:[~2015-08-06 0:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 19:05 [PATCH] VT-d: add iommu=igfx_off option to workaround graphics issues Ting-Wei Lan
2015-07-17 19:36 ` Andrew Cooper
2015-07-18 8:46 ` 藍挺瑋
2015-07-19 15:53 ` Julien Grall
2015-07-20 8:27 ` Andrew Cooper
2015-07-20 10:19 ` Julien Grall
2015-07-20 1:28 ` Tian, Kevin
2015-07-20 8:21 ` Andrew Cooper
2015-07-20 10:44 ` Ting-Wei Lan
2015-07-21 0:57 ` Tian, Kevin
2015-07-21 6:56 ` Jan Beulich
2015-07-21 7:05 ` Tian, Kevin
2015-07-21 7:16 ` Jan Beulich
2015-07-21 7:23 ` Tian, Kevin
2015-07-21 7:33 ` Jan Beulich
2015-07-23 16:41 ` Ting-Wei Lan
2015-07-20 8:46 ` Jan Beulich
2015-07-25 16:57 ` [PATCH v2] VT-d: add iommu=igfx " Ting-Wei Lan
2015-07-26 16:47 ` Andrew Cooper
2015-07-31 1:26 ` Tian, Kevin
2015-07-31 8:37 ` Ting-Wei Lan
2015-08-04 2:00 ` Tian, Kevin
2015-08-05 9:11 ` [PATCH v3] " Ting-Wei Lan
2015-08-05 12:18 ` Andrew Cooper
2015-08-05 13:35 ` Wei Liu
2015-08-05 17:10 ` [PATCH v4] " Ting-Wei Lan
2015-08-06 0:49 ` Tian, Kevin [this message]
2015-08-06 8:25 ` Wei Liu
2015-08-06 9:28 ` Ian Campbell
2015-07-20 12:12 ` [PATCH] VT-d: add iommu=igfx_off " Andrew Cooper
2015-07-20 12:24 ` Jan Beulich
2015-07-20 12:34 ` Andrew Cooper
2015-07-20 13:55 ` Jan Beulich
2015-07-20 14:12 ` Andrew Cooper
2015-07-20 14:25 ` Jan Beulich
2015-07-21 1:15 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AADFC41AFE54684AB9EE6CBC0274A5D142ABF266@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@citrix.com \
--cc=lantw44@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).