From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thierry Laurion <thierry.laurion@gmail.com>
Subject: Re: pre Sandy bridge IOMMU support (gm45)
Date: Sun, 24 Jan 2016 18:21:05 +0000
Message-ID: <CAAzJznzd67WAk=GQQDCZWETxQO1BGS+-AWHuKpWkNVJCbCqpbw@mail.gmail.com>
References: <CAAzJznzyDqyuSBZOJowGnFKDBKYSTrhLge18wggG0uycYHPaRQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=001a113deb7c956751052a188499
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAAzJznzyDqyuSBZOJowGnFKDBKYSTrhLge18wggG0uycYHPaRQ@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org, qubes-devel <qubes-devel@googlegroups.com>
List-Id: xen-devel@lists.xenproject.org

--001a113deb7c956751052a188499
Content-Type: multipart/alternative; boundary=001a113deb7c95674d052a188497

--001a113deb7c95674d052a188497
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi devs!

XEN devs:
As per short discussion with ktemkin earlier in January in #xen:

"ktemkin Jan 10, 2016 16:21:50
This test patch did appear to make the system work, though:
https://gist.github.com/ktemkin/0e81b93654ae800a5609

ktemkin Jan 10, 2016 16:24:55
Only real difference I see between that and the upstream behavior (besides
limiting things to dom0 so things weren't accidentally passed through) is
the call to disable_pmr on line 117 before aborting."



Makes total sense to my early understanding, since it seems that it is said
that vt-d engine gets disabled, but disable_pmr(iommu) function is not
called to enforce.

What do you think?

QUBES devs:
I'm still trying to understand how to apply this patch to qubes_builder to
actually build a test iso or xen.gz image and report. All Qubes patches
seem to be applied from git to local directory structure. Looking inside
the code to understand how to generate the provided patch to git can apply
it to local chrooted environment when building. Any documentation you could
point me to would be greatly appreciated, as any feedback to actually fix
the issue stopping this laptop from being a nearly perfect candidate for
Qubes.


Thierry

Le sam. 23 janv. 2016 =C3=A0 02:37, Thierry Laurion <thierry.laurion@gmail.=
com>
a =C3=A9crit :

> Hey devs,
>
> Thinkpad x200 p8600 laptops have vt-d, vt-x and tpm. They also have intel
> integrated graphics 4 Series (gm45 chipset), supported through i915 drive=
r.
>
> In December, a fix got introduced to Xen 4.6 through iommu=3Dno-igfx swit=
ch.
> Before that fix, it was impossible to boot xen without passing iommu=3D0.
>
> With iommu=3Dno-igfx passed on, Qubes boots xen, kernel, dom0 and domu un=
til
> some graphic rendering is done from a domu to dom0 xserver.
>
> I'm trying to push forward IOMMU support of gm45 chipset here. The proble=
m
> is between i915 and xen iommu support for sure, but there is no crash or
> interesting debugging information given on a serial console.
>
> Any dev help is welcome since that beast and t400 would be excellent Qube=
s
> candidates once that problem is fixed. I posted in December on the list
> just before Christmas but I guess the timing wasn't right;)
>
> Thanks for your help.
> Thierry
>

--001a113deb7c95674d052a188497
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Hi devs!<br><br></div>XEN devs:<br>As =
per short discussion with ktemkin earlier in January in #xen:<br><br>&quot;=
ktemkin Jan 10, 2016 16:21:50<br>This test patch did appear to make the sys=
tem work, though: <a rel=3D"nofollow" target=3D"_blank" href=3D"https://gis=
t.github.com/ktemkin/0e81b93654ae800a5609">https://gist.github.com/ktemkin/=
0e81b93654ae800a5609</a><br><br>ktemkin Jan 10, 2016 16:24:55<br>Only real =
difference I see between that and the upstream behavior (besides limiting t=
hings to dom0 so things weren&#39;t accidentally passed through) is the cal=
l to disable_pmr on line 117 before aborting.&quot;<br><br><br><br></div>Ma=
kes total sense to my early understanding, since it seems that it is said t=
hat vt-d engine gets disabled, but disable_pmr(iommu) function is not calle=
d to enforce.<br><br></div>What do you think?<br><br></div>QUBES devs:<br>I=
&#39;m still trying to understand how to apply this patch to qubes_builder =
to actually build a test iso or xen.gz image and report. All Qubes patches =
seem to be applied from git to local directory structure. Looking inside th=
e code to understand how to generate the provided patch to git can apply it=
 to local chrooted environment when building. Any documentation you could p=
oint me to would be greatly appreciated, as any feedback to actually fix th=
e issue stopping this laptop from being a nearly perfect candidate for Qube=
s.<br><br><br><div><div>Thierry<br></div><div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr">Le=C2=A0sam. 23 janv. 2016 =C3=A0=C2=A002:37, Thierry La=
urion &lt;<a href=3D"mailto:thierry.laurion@gmail.com">thierry.laurion@gmai=
l.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">H=
ey devs,<br><br>Thinkpad x200 p8600 laptops have vt-d, vt-x and tpm. They a=
lso have intel integrated graphics 4 Series (gm45 chipset), supported throu=
gh i915 driver. <br><br>In December, a fix got introduced to Xen 4.6 throug=
h iommu=3Dno-igfx switch. Before that fix, it was impossible to boot xen wi=
thout passing iommu=3D0.<br><br>With iommu=3Dno-igfx passed on, Qubes  boot=
s xen, kernel, dom0 and domu until some graphic rendering is done from a do=
mu to dom0 xserver.<br><br>I&#39;m trying to push forward IOMMU support of =
gm45 chipset here. The problem is between i915 and xen iommu support for su=
re, but there is no crash or interesting debugging information given on a s=
erial console.<br><br>Any dev help is welcome since that beast and t400 wou=
ld be excellent Qubes candidates once that problem is fixed. I posted in De=
cember on the list just before Christmas but I guess the timing wasn&#39;t =
right;)<div><br></div><div>Thanks for your help.</div><div>Thierry</div></b=
lockquote></div></div></div></div>

--001a113deb7c95674d052a188497--

--001a113deb7c956751052a188499
Content-Type: text/x-patch; charset=US-ASCII; name="xen.diff"
Content-Disposition: attachment; filename="xen.diff"
Content-Transfer-Encoding: base64
Content-ID: <15274d2c87e4ecec2b21>
X-Attachment-Id: 15274d2c87e4ecec2b21

LS0tIC4vZHJpdmVycy9wYXNzdGhyb3VnaC92dGQvaW9tbXUuYy5iYWsJMjAxNi0wMS0yNCAxMjo1
NToxNS4wMjAyNjc1NTMgLTA1MDAKKysrIC4vZHJpdmVycy9wYXNzdGhyb3VnaC92dGQvaW9tbXUu
YwkyMDE2LTAxLTI0IDEyOjU3OjE0Ljc1NDEzODI2MiAtMDUwMApAQCAtNzE3LDYgKzcxNyw3IEBA
CiAgICAgICAgIHsKICAgICAgICAgICAgIGRwcmludGsoWEVOTE9HX1dBUk5JTkcgVlREUFJFRklY
LAogICAgICAgICAgICAgICAgICAgICAiQklPUyBkaWQgbm90IGVuYWJsZSBJR0QgZm9yIFZUIHBy
b3Blcmx5LiAgRGlzYWJsaW5nIElHRCBWVC1kIGVuZ2luZS5cbiIpOworICAgICAgICAgICAgZGlz
YWJsZV9wbXIoaW9tbXUpOwogICAgICAgICAgICAgcmV0dXJuOwogICAgICAgICB9CiAgICAgfQo=
--001a113deb7c956751052a188499
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--001a113deb7c956751052a188499--