All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>,
	weidong.han@intel.com, allen.m.kay@intel.com
Cc: xen-devel@lists.xensource.com, Jean Guyader <jean.guyader@gmail.com>
Subject: Re: Problem: Pattern with vertical colored lines on the dom0 screen
Date: Mon, 27 Sep 2010 12:47:06 -0400	[thread overview]
Message-ID: <20100927164706.GC4741@dumpdata.com> (raw)
In-Reply-To: <201009271406.26670.dietmar.hahn@ts.fujitsu.com>

On Mon, Sep 27, 2010 at 02:06:26PM +0200, Dietmar Hahn wrote:
> Hi Jean,
> 
> many thanks for this hint! This saved me a lot of time searching through
> the specs.
> 
> Am 24.09.2010 schrieb Jean Guyader:
> > The problem we saw with that the bit 10 of the GCC (offset 0x52 on the
> > PCH config space)
> > wasn't set after the bios. This bit probably enable the shadow GTT
> > (created with the GTT + vt-d).
> 
> Yes, the same problem here!
> I found the following patch, maybe something similar would help here too?
> https://patchwork.kernel.org/patch/132771

There looks to be another in the upstream kernels:

check_tylersburg_isoch
> 
> So I have to hit the bios development :-(

Well, we should probably provide a quirk check in the Xen code.

Copying the Intel folks to see if they any ideas on adding this in the Intel VT-d
code paths. Or they might have already a patch ready for this?
> 
> > The vertical stripes means GTT fault.
> > 
> > Jean
> 
> Many thanks!
> Dietmar.
> 
> -- 
> Company details: http://ts.fujitsu.com/imprint.html
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-09-27 16:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 13:20 Problem: Pattern with vertical colored lines on the dom0 screen Dietmar Hahn
2010-09-20 20:59 ` Konrad Rzeszutek Wilk
2010-09-21  7:19   ` Dietmar Hahn
2010-09-21 14:42     ` Konrad Rzeszutek Wilk
2010-09-22 13:06       ` Dietmar Hahn
2010-09-22 13:56         ` Konrad Rzeszutek Wilk
2010-09-23 11:53           ` Dietmar Hahn
2010-09-24  9:50             ` Dietmar Hahn
2010-09-22 14:23         ` Jan Beulich
2010-09-23 11:53           ` Dietmar Hahn
2010-09-24 10:19 ` Jean Guyader
2010-09-24 11:10   ` Dietmar Hahn
2010-09-24 11:23     ` Jean Guyader
2010-09-27 12:06       ` Dietmar Hahn
2010-09-27 16:47         ` Konrad Rzeszutek Wilk [this message]
2010-09-28 23:54           ` Kay, Allen M
2010-09-29  6:04             ` Pasi Kärkkäinen
2010-09-29 16:14               ` Kay, Allen M
2010-09-29 19:17                 ` Pasi Kärkkäinen
2010-09-29 23:14           ` Kay, Allen M
2010-09-30  7:58             ` Dietmar Hahn
2010-10-04  8:23             ` Jan Beulich
2010-10-04 15:11               ` Kay, Allen M
2010-10-04 15:24                 ` Jan Beulich
2010-10-04 18:15                   ` Kay, Allen M
2010-10-05  6:51                     ` Jan Beulich
2010-10-05 23:20                       ` Kay, Allen M
  -- strict thread matches above, loose matches on Subject: below --
2010-10-08 20:33 Eric Riser

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=20100927164706.GC4741@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=allen.m.kay@intel.com \
    --cc=dietmar.hahn@ts.fujitsu.com \
    --cc=jean.guyader@gmail.com \
    --cc=weidong.han@intel.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.