public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 9/9] drm/i915: swizzling support for snb/ivb
Date: Fri, 11 Nov 2011 18:22:25 +0100	[thread overview]
Message-ID: <20111111172225.GB7295@phenom.ffwll.local> (raw)
In-Reply-To: <87sjluob6x.fsf@eliezer.anholt.net>

On Fri, Nov 11, 2011 at 08:50:30AM -0800, Eric Anholt wrote:
> On Thu, 10 Nov 2011 14:18:07 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > We have to do this manually. Somebody had a Great Idea.
> > 
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> People playing with this when not strictly required is scary to me.
> Manually swizzling was a world of hurt.  I got to play with things like
> "when the management engine is enabled, it carves out the top N MB of
> one of the dimms, and the corresponding N MB of the other dimm doesn't
> get swizzled, and you lose".

Looks like yet another patch series of mine that scares away people ...

Would this patch be less scary when we have a test that slurps in the
entire ram to quickly diagnose such issues? We can then either revert this
or fix up the detection to not enable swizzling in such cases.

Also the manually swizzling is a world of hurt argument is pretty void: Up
to very recent kernels we've advertised bit9 swizzling on snb+ without any
swizzling actually going on. So userspace clearly doesn't rely on this
anymore (the issue was caught by running the pread tests in i-g-t).

Also we already have a bug for gm45 which looks like a portion of ram
isn't swizzled:
https://bugs.freedesktop.org/show_bug.cgi?id=28813

-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2011-11-11 17:21 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 [this message]
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
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=20111111172225.GB7295@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eric@anholt.net \
    --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