From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>, stable@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: check the right ring in radeon_evict_flags()
Date: Wed, 03 Dec 2014 17:10:44 +0100 [thread overview]
Message-ID: <547F3604.2030702@vodafone.de> (raw)
In-Reply-To: <1417622966-23949-1-git-send-email-alexander.deucher@amd.com>
Am 03.12.2014 um 17:09 schrieb Alex Deucher:
> Check the that ring we are using for copies is functional
> rather than the GFX ring. On newer asics we use the DMA
> ring for bo moves.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/radeon/radeon_ttm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c
> index cbe7b32..d02aa1d 100644
> --- a/drivers/gpu/drm/radeon/radeon_ttm.c
> +++ b/drivers/gpu/drm/radeon/radeon_ttm.c
> @@ -196,7 +196,7 @@ static void radeon_evict_flags(struct ttm_buffer_object *bo,
> rbo = container_of(bo, struct radeon_bo, tbo);
> switch (bo->mem.mem_type) {
> case TTM_PL_VRAM:
> - if (rbo->rdev->ring[RADEON_RING_TYPE_GFX_INDEX].ready == false)
> + if (rbo->rdev->ring[radeon_copy_ring_index(rbo->rdev)].ready == false)
> radeon_ttm_placement_from_domain(rbo, RADEON_GEM_DOMAIN_CPU);
> else if (rbo->rdev->mc.visible_vram_size < rbo->rdev->mc.real_vram_size &&
> bo->mem.start < (rbo->rdev->mc.visible_vram_size >> PAGE_SHIFT)) {
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-12-03 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:09 [PATCH] drm/radeon: check the right ring in radeon_evict_flags() Alex Deucher
2014-12-03 16:10 ` Christian König [this message]
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=547F3604.2030702@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@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.