From 9ac5504df5c31e60801d9d37c1f3d547c486bf0a Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Fri, 1 Dec 2017 00:06:34 +0100 Subject: gallium/radeon: move setting VRAM|GTT into winsyses MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The combined VRAM|GTT heap will be removed. Reviewed-by: Nicolai Hähnle --- src/gallium/drivers/radeon/r600_buffer_common.c | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'src/gallium/drivers/radeon') diff --git a/src/gallium/drivers/radeon/r600_buffer_common.c b/src/gallium/drivers/radeon/r600_buffer_common.c index d162eeae662..ec282d55aaf 100644 --- a/src/gallium/drivers/radeon/r600_buffer_common.c +++ b/src/gallium/drivers/radeon/r600_buffer_common.c @@ -171,20 +171,6 @@ void si_init_resource_fields(struct si_screen *sscreen, else res->flags |= RADEON_FLAG_NO_INTERPROCESS_SHARING; - /* If VRAM is just stolen system memory, allow both VRAM and - * GTT, whichever has free space. If a buffer is evicted from - * VRAM to GTT, it will stay there. - * - * DRM 3.6.0 has good BO move throttling, so we can allow VRAM-only - * placements even with a low amount of stolen VRAM. - */ - if (!sscreen->info.has_dedicated_vram && - (sscreen->info.drm_major < 3 || sscreen->info.drm_minor < 6) && - res->domains == RADEON_DOMAIN_VRAM) { - res->domains = RADEON_DOMAIN_VRAM_GTT; - res->flags &= ~RADEON_FLAG_NO_CPU_ACCESS; /* disallowed with VRAM_GTT */ - } - if (sscreen->debug_flags & DBG(NO_WC)) res->flags &= ~RADEON_FLAG_GTT_WC; -- cgit v1.2.3