Mesa (master): svga: Undo the DMA buffer size limiting.
Jose Fonseca
jrfonseca at kemper.freedesktop.org
Mon Mar 21 18:47:35 UTC 2011
Module: Mesa
Branch: master
Commit: 29288249e35693a33b7873ed11b09c313b2e49f0
URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=29288249e35693a33b7873ed11b09c313b2e49f0
Author: José Fonseca <jfonseca at vmware.com>
Date: Thu Mar 17 23:33:50 2011 +0000
svga: Undo the DMA buffer size limiting.
Move this to the winsys, given it is not a virtual device limitation,
but a limitation specific to certain winsyses.
Also update debug message.
---
.../drivers/svga/svga_resource_buffer_upload.c | 15 ++-------------
1 files changed, 2 insertions(+), 13 deletions(-)
diff --git a/src/gallium/drivers/svga/svga_resource_buffer_upload.c b/src/gallium/drivers/svga/svga_resource_buffer_upload.c
index e5fcec0..9239586 100644
--- a/src/gallium/drivers/svga/svga_resource_buffer_upload.c
+++ b/src/gallium/drivers/svga/svga_resource_buffer_upload.c
@@ -40,9 +40,6 @@
#include "svga_debug.h"
-#define MAX_DMA_SIZE (4 * 1024 * 1024)
-
-
/**
* Allocate a winsys_buffer (ie. DMA, aka GMR memory).
*
@@ -60,18 +57,10 @@ svga_winsys_buffer_create( struct svga_context *svga,
struct svga_winsys_screen *sws = svgascreen->sws;
struct svga_winsys_buffer *buf;
- /* XXX this shouldn't be a hard-coded number; it should be queried
- * somehow.
- */
- if (size > MAX_DMA_SIZE) {
- return NULL;
- }
-
/* Just try */
buf = sws->buffer_create(sws, alignment, usage, size);
- if(!buf) {
-
- SVGA_DBG(DEBUG_DMA|DEBUG_PERF, "flushing screen to find %d bytes GMR\n",
+ if (!buf) {
+ SVGA_DBG(DEBUG_DMA|DEBUG_PERF, "flushing context to find %d bytes GMR\n",
size);
/* Try flushing all pending DMAs */
More information about the mesa-commit
mailing list