From: Andi Kleen <andi@firstfloor.org>
To: "Stéphane Marchesin" <marcheu@chromium.org>
Cc: linux-kernel@vger.kernel.org, keithp@keithp.com,
torvalds@linux-foundation.org, seanpaul@chromium.org,
olofj@chromium.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] mm: Work around Intel SNB GTT bug with some physical pages.
Date: Mon, 07 May 2012 16:57:09 -0700 [thread overview]
Message-ID: <m2zk9jlf3e.fsf@firstfloor.org> (raw)
In-Reply-To: <1336432421-17972-1-git-send-email-marcheu@chromium.org> ("Stéphane Marchesin"'s message of "Mon, 7 May 2012 16:13:41 -0700")
Stéphane Marchesin <marcheu@chromium.org> writes:
> While investing some Sandy Bridge rendering corruption, I found out
> that all physical memory pages below 1MiB were returning garbage when
> read through the GTT. This has been causing graphics corruption (when
> it's used for textures, render targets and pixmaps) and GPU hangups
> (when it's used for GPU batch buffers).
It would be possible to exlude GFP_DMA from the page allocator. That
covers the first 16MB. You just need a custom zone list with ZONE_DMA.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-05-07 23:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 23:13 [PATCH] mm: Work around Intel SNB GTT bug with some physical pages Stéphane Marchesin
2012-05-07 23:57 ` Andi Kleen [this message]
2012-05-08 6:53 ` Dave Airlie
2012-05-08 7:21 ` Daniel Vetter
2012-05-08 15:25 ` Linus Torvalds
2012-05-08 15:25 ` Linus Torvalds
2012-05-08 17:23 ` Daniel Vetter
2012-05-08 18:03 ` Rob Clark
2012-05-08 21:57 ` Hugh Dickins
2012-05-09 8:56 ` Daniel Vetter
2012-05-09 8:56 ` 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=m2zk9jlf3e.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=olofj@chromium.org \
--cc=seanpaul@chromium.org \
--cc=torvalds@linux-foundation.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 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.