From: Thierry Laurion <thierry.laurion@gmail.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: pre Sandy bridge IOMMU support (gm45)
Date: Tue, 26 Jan 2016 23:39:00 +0000 [thread overview]
Message-ID: <CAAzJznx82jCy_u_n4s11H_eeZuyVpzHyuuUObOBgf=Y1Ux+wPQ@mail.gmail.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F78ECE7@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
It seems that IGD iommu is not completely deactivated, yes, since memory
corruption happens (graphic glitches and then system hang)
General iommu is still reported as being active by xen, as desired.
Thierry
Le mar. 26 janv. 2016 17:21, Tian, Kevin <kevin.tian@intel.com> a écrit :
> > From: Jan Beulich
> > Sent: Tuesday, January 26, 2016 8:28 PM
> >
> > >>> On 26.01.16 at 12:57, <thierry.laurion@gmail.com> wrote:
> > > Only dom0 talks directly to the i915 driver, other appvm being pv,
> which is
> > > why I put in question the complete deactivation of IGD by
> iommu=no-igfx.
> > >
> > > Is there anything I can provide to troubleshoot?
> >
> > Hard to tell. The VT-d maintainers may be able to give you better
> > guidance.
> >
> > Jan
> >
>
> I'm a bit confused what's being exactly asked here. Did you mean
> that IOMMU is not actually disabled when you set iommu=no-gfx?
>
> Thanks
> Kevin
>
[-- Attachment #1.2: Type: text/html, Size: 1379 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-26 23:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 7:38 pre Sandy bridge IOMMU support (gm45) Thierry Laurion
2016-01-24 18:21 ` Thierry Laurion
2016-01-24 23:45 ` [qubes-devel] " Marek Marczykowski-Górecki
2016-01-26 21:10 ` Thierry Laurion
2016-01-27 5:08 ` Thierry Laurion
2016-01-29 17:52 ` Thierry Laurion
2016-01-25 10:01 ` Andrew Cooper
2016-01-25 14:30 ` Jan Beulich
2016-01-25 21:49 ` Thierry Laurion
2016-01-26 10:52 ` Jan Beulich
[not found] ` <CAAzJznxr4CT8J0fnx1kkWfQ+56J0PH+QBjgjH=6phtzbDd4dyw@mail.gmail.com>
2016-01-26 11:37 ` Jan Beulich
2016-01-26 11:57 ` Thierry Laurion
2016-01-26 12:27 ` Jan Beulich
2016-01-26 22:21 ` Tian, Kevin
2016-01-26 23:39 ` Thierry Laurion [this message]
2016-01-30 1:47 ` Marek Marczykowski-Górecki
2016-02-01 7:59 ` Jan Beulich
2016-02-01 12:28 ` Marek Marczykowski-Górecki
2016-02-01 12:35 ` Jan Beulich
2016-02-20 18:20 ` Thierry Laurion
2016-02-21 3:45 ` Thierry Laurion
2016-02-28 19:08 ` Thierry Laurion
2016-06-26 23:47 ` Thierry Laurion
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='CAAzJznx82jCy_u_n4s11H_eeZuyVpzHyuuUObOBgf=Y1Ux+wPQ@mail.gmail.com' \
--to=thierry.laurion@gmail.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
/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).