On Thu, Oct 29, 2009 at 11:32 PM, Dave Airlie <airl...@gmail.com> wrote:
> From: Dave Airlie <airl...@redhat.com>
>
> When we are evicting from VRAM->RAM we allocate the ttm object,
> but we don't set the caching policy on it before blitting into it.
> This means on AGP we end up blitting into cached pages, and
> the CPU later flushes out on top of them. This was mostly seen as
> font corruption.
>
While we are here, are the PT snoop bits and caching set properly on
pages in non-AGP gart?
Alex
> The other question is why we don't evict VRAM->GTT in a lot of cases,
> this would save us some cache transitions since a lot of objects
> that are evicted from VRAM will probably end up being pulled back in
> a few operations later, and evicting them to system memory involves
> 2 unnecessary cache transitions.
>
> Signed-off-by: Dave Airlie <airl...@redhat.com>
> ---
> drivers/gpu/drm/radeon/radeon_ttm.c | 6 ++++++
> drivers/gpu/drm/ttm/ttm_tt.c | 1 +
> 2 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c
> b/drivers/gpu/drm/radeon/radeon_ttm.c
> index c729cd1..f489c0d 100644
> --- a/drivers/gpu/drm/radeon/radeon_ttm.c
> +++ b/drivers/gpu/drm/radeon/radeon_ttm.c
> @@ -295,6 +295,12 @@ static int radeon_move_vram_ram(struct ttm_buffer_object
> *bo,
> if (unlikely(r)) {
> return r;
> }
> +
> + r = ttm_tt_set_placement_caching(bo->ttm, tmp_mem.placement);
> + if (unlikely(r)) {
> + goto out_cleanup;
> + }
> +
> r = ttm_tt_bind(bo->ttm, &tmp_mem);
> if (unlikely(r)) {
> goto out_cleanup;
> diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
> index a55ee1a..7bcb89f 100644
> --- a/drivers/gpu/drm/ttm/ttm_tt.c
> +++ b/drivers/gpu/drm/ttm/ttm_tt.c
> @@ -279,6 +279,7 @@ int ttm_tt_set_placement_caching(struct ttm_tt *ttm,
> uint32_t placement)
>
> return ttm_tt_set_caching(ttm, state);
> }
> +EXPORT_SYMBOL(ttm_tt_set_placement_caching);
>
> static void ttm_tt_free_alloced_pages(struct ttm_tt *ttm)
> {
> --
> 1.6.5.1
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
