From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ting-Wei Lan <lantw44@gmail.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] VT-d: add iommu=igfx_off option to workaround graphics issues
Date: Tue, 21 Jul 2015 01:15:18 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D1262CDE82@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <55AD04890200007800093114@mail.emea.novell.com>
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Monday, July 20, 2015 8:24 PM
>
> >>> On 20.07.15 at 14:12, <andrew.cooper3@citrix.com> wrote:
> > On 17/07/15 20:05, Ting-Wei Lan wrote:
> >> 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_off option that is similar to Linux intel_iommu=igfx_off for
> >> users to manually workaround the problem.
> >>
> >> Signed-off-by: Ting-Wei Lan <lantw44@gmail.com>
> >
> > Having looked into this issue, the i915 driver has several workarounds
> > in it for systems when the IOMMU is in use. In some cases there are
> > plain errata, while in other cases there are specific hardware features
> > which don't function if the IOMMU is enabled.
> >
> > In all cases this is gated on Linux's idea of whether the IOMMU is
> > enabled. When used under Xen, Linux has no clue that the IOMMU exists,
> > or that Xen has turned it on.
>
> Perhaps it should just assume an IOMMU is in use when running under
> Xen. Having inspected all those code places quite some time ago, I
> came to the conclusion that making this assumption is better than
> the current one of there not being an enabled IOMMU (and I adjusted
> our kernels accordingly).
kind of agree here. IIRC, to have i915 working correctly in Dom0, user
needs to manually turn on CONFIG_DMAR and CONFIG_INTEL_IOMMU
although there's no IOMMU exposed. Otherwise i915 driver will use plain
virt_to_phys when programming GTT table which causes trouble.
Recently there are some improvements in this part, but still some IOMMU
specific tricks remain. So having the options default on under Xen looks
better.
Thanks
Kevin
prev parent reply other threads:[~2015-07-21 1:15 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
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 [this message]
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=AADFC41AFE54684AB9EE6CBC0274A5D1262CDE82@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=lantw44@gmail.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).