xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "G.R." <firemeteor.guo@gmail.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: intel IGD driver intel_detect_pch() failure
Date: Sun, 9 Dec 2012 00:23:31 +0800	[thread overview]
Message-ID: <CAKhsbWYd0R23yaaPJ43uSJaagBh_oCdP0=wt7GECzE8zKB9BSQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1408 bytes --]

Hi all,
I'm debugging an issue that an HVM guest failed to produce any output with
IGD passed through.
This is an pure HVM linux guest with i915 driver directly compiled in.
An PVHVM kernel with i915 driver compiled as module works without issue.
I'm not yet sure which factor is more important, pure HVM or the I915=y
kernel config.

The direct cause of no output is that the driver does not select Display
PLL properly, which is in turn due to fail to detect pch type properly.

Strange enough, the intel_detect_pch() function works by checking the
device ID of the ISA bridge coming with the chipset:

    /*
     * The reason to probe ISA bridge instead of Dev31:Fun0 is to
     * make graphics device passthrough work easy for VMM, that only
     * need to expose ISA bridge to let driver know the real hardware
     * underneath. This is a requirement from virtualization team.
     */

I added some debug output in this function and find out that it obtained a
strange device ID:
[    1.005423] [drm] intel pch detect, found 00007000

This looks like the ISA bridge provided by qemu:
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.0 0601: 8086:7000

However, I can find the same device on a PVHVM linux guest, but the
intel_detect_pch() is not fooled by that.
Is it due to I915=m config or some magic played by PVOPS? Any suggestion
how to fix this?

Thanks,
Timothy

[-- Attachment #1.2: Type: text/html, Size: 1524 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

             reply	other threads:[~2012-12-08 16:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08 16:23 G.R. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-08 17:43 intel IGD driver intel_detect_pch() failure G.R.
2012-12-09  5:00 ` G.R.
2012-12-10 11:12   ` G.R.
2012-12-10 12:26     ` Stefano Stabellini
2012-12-10 18:15       ` Kay, Allen M
2012-12-11  3:45         ` G.R.
2012-12-11 12:01           ` Stefano Stabellini
2012-12-11 14:29             ` G.R.
2012-12-11 15:10               ` Stefano Stabellini
2012-12-13  9:08                 ` G.R.
2012-12-13 12:43                   ` Stefano Stabellini
2012-12-13 14:33                     ` G.R.
2012-12-13 17:39                       ` G.R.
2012-12-14  2:39                         ` G.R.
2012-12-14 11:24                           ` G.R.
2012-12-14 12:59                             ` Stefano Stabellini
2012-12-14 14:42                               ` G.R.

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='CAKhsbWYd0R23yaaPJ43uSJaagBh_oCdP0=wt7GECzE8zKB9BSQ@mail.gmail.com' \
    --to=firemeteor.guo@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).