All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/Sandy Bridge: reserve pages when integrated graphics is present
Date: Wed, 14 Nov 2012 13:55:34 -0800	[thread overview]
Message-ID: <20121114135534.653b70dd@jbarnes-desktop> (raw)
In-Reply-To: <20121114211905.503f3701@pyramind.ukuu.org.uk>

On Wed, 14 Nov 2012 21:19:05 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> 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.
> 
> What happens if the other addresses map to an external memory object - eg
> a PCI device which is a legitimate DMA source for video overlay etc ?

Other addresses as in the 5 pages high in the address space?  I'm not
sure how to do what I want with memblock, doesn't it just allocate RAM
not I/O space?... /me looks at the memblock API

Or do you mean if we map GTT pages to point at some non-RAM region will
SNB gfx be able to decode them?  If that's the question, then I think
the answer is no, but I don't have enough detail on the hw bug to be
certain.

> I assume this is just for GPU fetches from main memory ?

AIUI, it's an address decoder bug, so it would affect any fetch by the
GPU through its memory interface glue.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2012-11-14 21:55 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 [this message]
2012-11-14 23:24     ` Alan Cox
2012-11-14 23:11 ` [Intel-gfx] " Jesse Barnes
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=20121114135534.653b70dd@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.