From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: "Matti Hämäläinen" <ccr@tnsp.org>, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915: Mark uneven memory banks on gen4 desktop as unknown swizzling
Date: Wed, 18 Nov 2015 10:05:17 +0000 [thread overview]
Message-ID: <20151118100517.GD14177@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1447756852-15183-1-git-send-email-chris@chris-wilson.co.uk>
On Tue, Nov 17, 2015 at 10:40:51AM +0000, Chris Wilson wrote:
> We have varied reports of swizzling corruption on gen4 desktop, and
> confirmation that it is triggered by uneven memory banks. The
> implication is that the swizzling various between the paired channels
> and the remainder of memory on the single channel. As the object then
> has unpredictable swizzling (it will vary depending on exact page
> allocation and may even change during the object's lifetime as the pages
> are replaced), we have to report to userspace that the swizzling is
> unknown.
>
> Reported-by: Matti H�m�l�inen <ccr@tnsp.org>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=90725
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matti H�m�l�inen <ccr@tnsp.org>
> Cc: stable@vger.kernel.org
Tested-by: Matti H�m�l�inen <ccr@tnsp.org>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2015-11-18 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 10:40 [PATCH 1/2] drm/i915: Mark uneven memory banks on gen4 desktop as unknown swizzling Chris Wilson
2015-11-17 10:40 ` [PATCH 2/2] drm/i915: Pin unknown swizzle pages Chris Wilson
2015-11-17 10:51 ` [PATCH 1/2] drm/i915: Mark uneven memory banks on gen4 desktop as unknown swizzling Chris Wilson
2015-11-18 10:05 ` Chris Wilson [this message]
2015-11-18 16:46 ` [Intel-gfx] " Daniel Vetter
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=20151118100517.GD14177@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=ccr@tnsp.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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