All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vc4: Allow using more than 256MB of CMA memory.
Date: Fri, 14 Apr 2017 11:07:20 -0700	[thread overview]
Message-ID: <8737da50dj.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170414100825.254b8181@bbrezillon>

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Boris Brezillon <boris.brezillon@free-electrons.com> writes:

> On Mon, 27 Mar 2017 16:10:25 -0700
> Eric Anholt <eric@anholt.net> wrote:
>
>> Until now, we've had to limit Raspberry Pi to 256MB of CMA memory to
>> keep from triggering the hardware addressing bug between of the tile
>> binner of the tile alloc memory (where the top 4 bits come from the
>> tile state data array's address).
>> 
>> To work around that and allow more memory to be reserved for graphics,
>> allocate a single BO to store tile state data arrays and tile
>> alloc/overflow memory while the GPU is active, and make sure that that
>> one BO doesn't happen to cross a 256MB boundary.  With that in place,
>> we can allocate textures and shaders anywhere in system memory (still
>> contiguous, of course).
>
> It's hard to review something I don't quite understand, but I didn't
> spot any problem and the code seems to follow what the commit message
> says: make sure the memory used by the tile binner (still have to look
> at what a tile binner is :-)) does not cross a 256MB.
>
> So, not sure my review has a real value here, but
>
> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>

It's still more review than vc4 patches used to get, so I'm happy.
Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/vc4: Allow using more than 256MB of CMA memory.
Date: Fri, 14 Apr 2017 11:07:20 -0700	[thread overview]
Message-ID: <8737da50dj.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170414100825.254b8181@bbrezillon>


[-- Attachment #1.1: Type: text/plain, Size: 1284 bytes --]

Boris Brezillon <boris.brezillon@free-electrons.com> writes:

> On Mon, 27 Mar 2017 16:10:25 -0700
> Eric Anholt <eric@anholt.net> wrote:
>
>> Until now, we've had to limit Raspberry Pi to 256MB of CMA memory to
>> keep from triggering the hardware addressing bug between of the tile
>> binner of the tile alloc memory (where the top 4 bits come from the
>> tile state data array's address).
>> 
>> To work around that and allow more memory to be reserved for graphics,
>> allocate a single BO to store tile state data arrays and tile
>> alloc/overflow memory while the GPU is active, and make sure that that
>> one BO doesn't happen to cross a 256MB boundary.  With that in place,
>> we can allocate textures and shaders anywhere in system memory (still
>> contiguous, of course).
>
> It's hard to review something I don't quite understand, but I didn't
> spot any problem and the code seems to follow what the commit message
> says: make sure the memory used by the tile binner (still have to look
> at what a tile binner is :-)) does not cross a 256MB.
>
> So, not sure my review has a real value here, but
>
> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>

It's still more review than vc4 patches used to get, so I'm happy.
Thanks!

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-04-14 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 23:10 [PATCH] drm/vc4: Allow using more than 256MB of CMA memory Eric Anholt
2017-03-27 23:10 ` Eric Anholt
2017-04-13  1:11 ` Eric Anholt
2017-04-13  1:11   ` Eric Anholt
2017-04-14  8:08 ` Boris Brezillon
2017-04-14  8:08   ` Boris Brezillon
2017-04-14 18:07   ` Eric Anholt [this message]
2017-04-14 18:07     ` Eric Anholt

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=8737da50dj.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=boris.brezillon@free-electrons.com \
    --cc=dri-devel@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.