public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 9/9] drm/i915: swizzling support for snb/ivb
Date: Mon, 14 Nov 2011 08:19:54 -0800	[thread overview]
Message-ID: <87lirid6c5.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <CAKMK7uF5=NBNsYSF0WmR0avcyo3=awWfFXiigxqUaLh4-sdEfw@mail.gmail.com>


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

On Fri, 11 Nov 2011 21:18:31 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Nov 11, 2011 at 20:58, Eric Anholt <eric@anholt.net> wrote:
> > Oh, yeah, swap.  Good point, sounds like a plan.  If you manage to get
> > reliable swapping of tiled data on 945g, I'll owe you all the beers.
> 
> If you mean i945G as in desktop variant, patch 6/9 should fix the
> swizzle detection on that one - it can do bit17 swizzling, too. I'd be
> interested in whether this fixes all the swap issues, if you have that
> machine still around ...
> 
> But as I've said there's also the gm45 bug which looks like a part of
> the main memory in not swizzled. On that topic: Do you still remember
> details about that machine where parts of the memory can be
> unswizzled?

The management engine/mismatched dimms issue making "L-shaped" memory
(part dual channel, part single channel) in the 945-gm45 era was never
handled (somewhere in g45-ilk era, there was a reg the BIOS could set
that would make L-shaped memory have consistent swizzling anyway).  I
never found precise docs on how to figure out what the shape of the L
was -- I suspect you'd get to find out by poking at things like TOLUD
and experimenting with binding all the pages you can grab to find which
are swizzled.


[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2011-11-14 16:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 13:17 [PATCH 0/9] gpu hang and swizzle patches Daniel Vetter
2011-11-10 13:17 ` [PATCH 1/9] drm/i915: refactor debugfs open function Daniel Vetter
2011-11-10 19:25   ` Ben Widawsky
2011-11-10 13:18 ` [PATCH 2/9] drm/i915: refactor debugfs create functions Daniel Vetter
2011-11-10 19:26   ` Ben Widawsky
2011-11-10 13:18 ` [PATCH 3/9] drm/i915: add interface to simulate gpu hangs Daniel Vetter
2011-11-10 16:34   ` [PATCH] " Daniel Vetter
2011-12-02 22:21     ` Daniel Vetter
2011-12-03  1:33       ` Chris Wilson
2011-12-05 23:20       ` Ben Widawsky
2011-11-10 13:18 ` [PATCH 4/9] drm/i915: rework dev->first_error locking Daniel Vetter
2011-11-27 19:31   ` [PATCH] " Daniel Vetter
2011-11-10 13:18 ` [PATCH 5/9] drm/i915: destroy existing error_state when simulating a gpu hang Daniel Vetter
2011-11-10 13:18 ` [PATCH 6/9] drm/i915: fix swizzle detection for gen3 Daniel Vetter
2011-11-10 16:36   ` [PATCH] " Daniel Vetter
2011-11-10 13:18 ` [PATCH 7/9] drm/i915: add debugfs file for swizzling information Daniel Vetter
2011-11-10 16:39   ` [PATCH] " Daniel Vetter
2011-11-10 13:18 ` [PATCH 8/9] drm/i915: add gen6+ registers to i915_swizzle_info Daniel Vetter
2011-11-10 13:18 ` [PATCH 9/9] drm/i915: swizzling support for snb/ivb Daniel Vetter
2011-11-11 16:50   ` Eric Anholt
2011-11-11 17:22     ` Daniel Vetter
2011-11-11 19:37       ` Eric Anholt
2011-11-11 19:51         ` Daniel Vetter
2011-11-11 19:58           ` Eric Anholt
2011-11-11 20:18             ` Daniel Vetter
2011-11-14 16:19               ` Eric Anholt [this message]
2011-11-11  0:15 ` [PATCH 0/9] gpu hang and swizzle patches Chris Wilson

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=87lirid6c5.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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