All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/etnaviv: move GPU linear window to end of DMA window
Date: Wed, 9 Mar 2016 12:25:08 +0000	[thread overview]
Message-ID: <20160309122507.GP19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1456762816-496-1-git-send-email-l.stach@pengutronix.de>

On Mon, Feb 29, 2016 at 05:20:16PM +0100, Lucas Stach wrote:
> If the end of the system DMA window is farther away from the start of
> physical RAM than the size of the GPU linear window, move the linear
> window so that it ends at the same address than the system DMA window.
> 
> This allows to map command buffer from CMA, which is likely to reside
> at the end of the system DMA window, while also overlapping as much
> RAM as possible, in order to optimize regular buffer mappings through
> the linear window.

I've been pondering this for a while now, and I think we should not
do this unconditionally - it should be predicated on the MC20 feature -
both for the original code and the new code.  If we don't have the MC20
feature, we end up with more memory spaces than we can cope with.

If we don't have MC20, but we need to offset, that's an error which
can lead to memory corruption.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-03-09 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 16:20 [PATCH] drm/etnaviv: move GPU linear window to end of DMA window Lucas Stach
2016-03-09 12:25 ` Russell King - ARM Linux [this message]
2016-03-14 15:02   ` Lucas Stach
2016-03-14 15:09     ` Russell King - ARM Linux
2016-03-14 15:18       ` Lucas Stach
2016-03-15  7:54         ` 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=20160309122507.GP19428@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=l.stach@pengutronix.de \
    /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.