From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] x86/Sandy Bridge: reserve pages when integrated graphics is present
Date: Wed, 14 Nov 2012 15:11:34 -0800 [thread overview]
Message-ID: <20121114151134.2df4d666@jbarnes-desktop> (raw)
In-Reply-To: <1352925811-2598-1-git-send-email-jbarnes@virtuousgeek.org>
On Wed, 14 Nov 2012 20:43:31 +0000
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> SNB graphics devices have a bug that prevent them from accessing certain
> memory ranges, namely anything below 1M and in the pages listed in the
> table. So reserve those at boot if set detect a SNB gfx device on the
> CPU to avoid GPU hangs.
>
> Stephane Marchesin had a similar patch to the page allocator awhile
> back, but rather than reserving pages up front, it leaked them at
> allocation time.
So if people are seeing seemingly random hangs with SNB, please give
this patch a try. These issues aren't easy to hit, and they're
frustratingly hard to debug, but with some long runtime maybe it'll
give people some confidence.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-11-14 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 20:43 [PATCH] x86/Sandy Bridge: reserve pages when integrated graphics is present Jesse Barnes
2012-11-14 21:19 ` Alan Cox
2012-11-14 21:55 ` Jesse Barnes
2012-11-14 23:24 ` Alan Cox
2012-11-14 23:11 ` Jesse Barnes [this message]
2012-11-15 12:47 ` Henrique de Moraes Holschuh
2012-11-15 16:13 ` Jesse Barnes
2012-11-15 16:14 ` Jesse Barnes
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=20121114151134.2df4d666@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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 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.