From: "Christian König" <deathsimple@vodafone.de>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/radeon: fix buffer placement under memory pressure v2
Date: Wed, 14 May 2014 11:46:46 +0200 [thread overview]
Message-ID: <53733B86.1070604@vodafone.de> (raw)
In-Reply-To: <CAAxE2A7HeTW_TCVs0oYP43Yjw2qv5vffKcrXhT9naQUJMZaBWQ@mail.gmail.com>
Am 13.05.2014 21:47, schrieb Marek Olšák:
> For the patch:
>
> Reviewed-by: Marek Olšák <marek.olsak@amd.com>
>
> It would be clearer if alt_domain was renamed to allowed_domains.
Yeah, already had the same idea. Going to rename "domain" to
"prefered_domains" and "alt_domain" to "allowed_domains" for 3.16.
Thanks,
Christian.
>
> Marek
>
> On Mon, May 12, 2014 at 3:30 PM, Christian König
> <deathsimple@vodafone.de> wrote:
>> From: Christian König <christian.koenig@amd.com>
>>
>> Some buffers (UVD/VM page tables) must be placed in VRAM,
>> but the byte restriction for moving buffers didn't took this
>> into account.
>>
>> v2: keep closer to the original code
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> ---
>> drivers/gpu/drm/radeon/radeon_object.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/radeon/radeon_object.c b/drivers/gpu/drm/radeon/radeon_object.c
>> index 72705fb..4faa4d6 100644
>> --- a/drivers/gpu/drm/radeon/radeon_object.c
>> +++ b/drivers/gpu/drm/radeon/radeon_object.c
>> @@ -458,7 +458,7 @@ int radeon_bo_list_validate(struct radeon_device *rdev,
>> * into account. We don't want to disallow buffer moves
>> * completely.
>> */
>> - if (current_domain != RADEON_GEM_DOMAIN_CPU &&
>> + if ((lobj->alt_domain & current_domain) != 0 &&
>> (domain & current_domain) == 0 && /* will be moved */
>> bytes_moved > bytes_moved_threshold) {
>> /* don't move it */
>> --
>> 1.9.1
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-14 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 13:30 [PATCH 1/2] drm/radeon: fix page directory update size estimation Christian König
2014-05-12 13:30 ` [PATCH 2/2] drm/radeon: fix buffer placement under memory pressure v2 Christian König
2014-05-13 19:47 ` Marek Olšák
2014-05-14 9:46 ` Christian König [this message]
2014-05-12 15:23 ` [PATCH 1/2] drm/radeon: fix page directory update size estimation Alex Deucher
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=53733B86.1070604@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=maraeo@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox