Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-07 Thread Marek Olšák
On Fri, Feb 7, 2014 at 3:55 AM, Michel Dänzer wrote: > On Mon, 2014-02-03 at 18:07 +0100, Marek Olšák wrote: >> Do you mean something like: >> >> write_domains = VRAM >> read_domains = VRAM | GTT >> >> I don't think it's perfect. > > That's what I meant, and of course it's not perfect. :) > > >> W

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-06 Thread Michel Dänzer
On Mon, 2014-02-03 at 18:07 +0100, Marek Olšák wrote: > Do you mean something like: > > write_domains = VRAM > read_domains = VRAM | GTT > > I don't think it's perfect. That's what I meant, and of course it's not perfect. :) > We should treat rendering by an app and blitting by u_blitter (= >

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-03 Thread Axel Davy
I don't know of any way to know if the buffer should be in GTT. There could also be the case where the buffer is first not shared with another device, and then is shared with another device. So at first we shouldn't have forced the buffer to stay in VRAM. Just to confirm, I have tested your p

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-03 Thread Marek Olšák
Do you mean something like: write_domains = VRAM read_domains = VRAM | GTT I don't think it's perfect. We should treat rendering by an app and blitting by u_blitter (= texture transfers) differently. We don't want u_blitter to mess up our idea about which textures are used as a framebuffer, becau

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-02 Thread Michel Dänzer
On Sam, 2014-02-01 at 15:08 +0100, Marek Olšák wrote: > From: Marek Olšák > > --- > src/gallium/drivers/radeon/r600_texture.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/gallium/drivers/radeon/r600_texture.c > b/src/gallium/drivers/radeon/r600_texture.c > index

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-02 Thread Marek Olšák
Well, it's kinda obvious what would happen. The buffer would be relocated to VRAM. Do you have any suggestion how to find out if the buffer should be in GTT instead? Marek On Mon, Feb 3, 2014 at 12:13 AM, Axel Davy wrote: >>From: Marek Olšák >> >>--- >> src/gallium/drivers/radeon/r600_texture.

Re: [Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-02 Thread Axel Davy
From: Marek Ols(ák http://lists.freedesktop.org/mailman/listinfo/mesa-dev>> --- src/gallium/drivers/radeon/r600_texture.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/radeon/r600_texture.c b/src/gallium/drivers/radeon/r600_texture.c index f80a6a2..434a65

[Mesa-dev] [PATCH 1/4] r600g, radeonsi: force VRAM placement for DRI2 buffers

2014-02-01 Thread Marek Olšák
From: Marek Olšák --- src/gallium/drivers/radeon/r600_texture.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/radeon/r600_texture.c b/src/gallium/drivers/radeon/r600_texture.c index f80a6a2..434a651 100644 --- a/src/gallium/drivers/radeon/r600_texture.c