xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Thierry Laurion <thierry.laurion@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: pre Sandy bridge IOMMU support (gm45)
Date: Mon, 25 Jan 2016 07:30:29 -0700	[thread overview]
Message-ID: <56A63F9502000078000CAAD1@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CAAzJznzyDqyuSBZOJowGnFKDBKYSTrhLge18wggG0uycYHPaRQ@mail.gmail.com>

>>> On 23.01.16 at 08:38, <thierry.laurion@gmail.com> wrote:
> Thinkpad x200 p8600 laptops have vt-d, vt-x and tpm. They also have intel
> integrated graphics 4 Series (gm45 chipset), supported through i915 driver.
> 
> In December, a fix got introduced to Xen 4.6 through iommu=no-igfx switch.
> Before that fix, it was impossible to boot xen without passing iommu=0.
> 
> With iommu=no-igfx passed on, Qubes boots xen, kernel, dom0 and domu until
> some graphic rendering is done from a domu to dom0 xserver.
> 
> I'm trying to push forward IOMMU support of gm45 chipset here. The problem
> is between i915 and xen iommu support for sure, but there is no crash or
> interesting debugging information given on a serial console.

To be honest, even after having read you second mail I'm not quite
clear what it you want and/or what doesn't work. Adding some
guessing, I could interpret the above as you wanting to pass through
the graphics device. If that's the case, then this is quite clearly a
pretty bad idea with the IOMMU behind it disabled.

Jan

  parent reply	other threads:[~2016-01-25 14:30 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 [this message]
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
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=56A63F9502000078000CAAD1@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=thierry.laurion@gmail.com \
    --cc=xen-devel@lists.xen.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).