On 10/16/2015 07:32 PM, Ilia Mirkin wrote:
Other than the missing * (1 << c), what was wrong with the old logic?
MP counters were always configured starting from slot 0 to cfg->num_src.
So, if you monitored two hardware events at the same time, the first one
was overwritten by the second
Other than the missing * (1 << c), what was wrong with the old logic?
On Fri, Oct 16, 2015 at 1:22 PM, Samuel Pitoiset
wrote:
> Queries which use more than one MP counters was misconfigured and
> computing the final result was also wrong because sources need to
> be
Series is Reviewed-by: Ilia Mirkin
I had a couple of very minor comments that you can feel free to accept
or ignore.
On Fri, Oct 16, 2015 at 1:22 PM, Samuel Pitoiset
wrote:
> MP counters on GF100/GF110 (compute capability 2.0) are buggy
>
Minor preferences for naming things SM20/SM21 when referring to
compute capabilities, but your call.
On Fri, Oct 16, 2015 at 1:22 PM, Samuel Pitoiset
wrote:
> GF100 and GF110 chipsets are compute capability 2.0, while the other
> Fermi chipsets are compute capability
On Fri, Oct 16, 2015 at 1:22 PM, Samuel Pitoiset
wrote:
> NOUVEAU_GETPARAM_GRAPH_UNITS param returns the number of GPCs, the total
> number of TPCs and the number of ROP units. Note that when the DRM
> version is too old the default number of GPCs is fixed to 4.
>
>
On 10/16/2015 07:50 PM, Ilia Mirkin wrote:
Series is Reviewed-by: Ilia Mirkin
I had a couple of very minor comments that you can feel free to accept
or ignore.
Thank you for this review Ilia, and I think I'll accept all of your
changes. :)
On Fri, Oct 16, 2015 at
Hello,
This series fixes some issues related to MP performance counters on Fermi.
MP counters for GF100/GF110 have also been improved because they are compute
capability 2.0 while the other Fermi chipsets are 2.1 and some HW events are
different.
Compute support is now enabled by default on
Because we can't expose the number of hardware counters needed for each
different query, we don't want to allow more than one active query
simultaneously to avoid failure when the maximum number of counters
is reached. Note that these groups of GPU counters are currently only
used by
MP counters on GF100/GF110 (compute capability 2.0) are buggy
because there is a context-switch problem that we need to fix.
Results might be wrong sometimes, be careful!
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c | 5 +
GF100 and GF110 chipsets are compute capability 2.0, while the other
Fermi chipsets are compute capability 2.1. That's why, some MP counters
are different between these chipsets and we need to handle variants.
Signed-off-by: Samuel Pitoiet
---
When a card has more than one GPC, the grid used by the compute
kernel which reads MP performance counters seems to be too small.
The consequence is that the kernel is not launched on all TPCs.
Increasing the grid size using the number of GPCs now launches
enough blocks and we can read MP
This will help for handling HW SM queries variants on Fermi.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query.c | 185 +
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw.c | 14 ++
On Fermi, we have one domain of 8 MP counters while we have
two domains of 4 MP counters on Kepler.
Signed-off-by: Samuel Pitoiset
---
.../drivers/nouveau/nvc0/nvc0_query_hw_sm.c| 30 +-
.../drivers/nouveau/nvc0/nvc0_query_hw_sm.h|
The way we configure MP performance counters is going to pretty
different between Fermi and Kepler. Having two separate functions
is much better.
Signed-off-by: Samuel Pitoiset
---
.../drivers/nouveau/nvc0/nvc0_query_hw_sm.c| 108 -
1 file
For strange reasons, the signal id depends on the slot selected on Fermi
but not on Kepler. Fortunately, the signal ids are just offseted by the
slot id!
Signed-off-by: Samuel Pitoiset
---
.../drivers/nouveau/nvc0/nvc0_query_hw_sm.c| 147 +++--
Compute support was not enabled by default because weird effects
on 3D state happened, but I can't reproduce them anymore.
This also enables MP performance counters by default on Fermi.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query.c
Sequence fields are located at MP[i] + 0x20 in the buffer object.
This is used to check if result is available for MP[i].
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Queries which use more than one MP counters was misconfigured and
computing the final result was also wrong because sources need to
be configured on different hardware counters instead.
According to the blob, computing the result is now as follows:
FOR i..n
val += ctr[i] * pow(2, i)
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c
b/src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c
Writing 0x408000 to 0x419e00 (like on Kepler) has no effect on Fermi
because we only have one domain of 8 counters. Instead, we have to
write 0x8000.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c | 5 +
1 file changed,
Writing 0x1fcb to 0x419eac is definitely not related to MP counters and
has no effect on Fermi (although this enables MP counters on Kepler).
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/nvc0_query_hw_sm.c | 8 +---
1 file changed, 1
Memory access have to be aligned to 128-bits. Note that this
doesn't happen when the card only has TPC.
This patch fixes the following dmesg fail:
gr: GPC0/TPC1/MP trap: global 0004 [MULTIPLE_WARP_ERRORS] warp 000f
[UNALIGNED_MEM_ACCESS]
Signed-off-by: Samuel Pitoiset
NOUVEAU_GETPARAM_GRAPH_UNITS param returns the number of GPCs, the total
number of TPCs and the number of ROP units. Note that when the DRM
version is too old the default number of GPCs is fixed to 4.
This will be used to launch the compute kernel which is used to read MP
performance counters
On 10/16/2015 07:24 PM, Ilia Mirkin wrote:
On Fri, Oct 16, 2015 at 1:22 PM, Samuel Pitoiset
wrote:
NOUVEAU_GETPARAM_GRAPH_UNITS param returns the number of GPCs, the total
number of TPCs and the number of ROP units. Note that when the DRM
version is too old the
On Fri, Oct 16, 2015 at 2:58 AM, Iago Toral Quiroga wrote:
> Now that we have separate index spaces for UBOs and SSBOs we do not need
> to iterate through BufferInterfaceBlocks any more, we can just take the
> UBO count directly from NumUniformBlocks.
Nice cleanup, all five
On 10/16/2015 11:57 PM, Ilia Mirkin wrote:
On Fri, Oct 16, 2015 at 5:35 PM, Samuel Pitoiset
wrote:
On 10/16/2015 11:22 PM, Ilia Mirkin wrote:
On Fri, Oct 16, 2015 at 5:29 PM, Samuel Pitoiset
wrote:
As explained in the CUDA toolkit
On 15/10/15 15:51, Brian Paul wrote:
Fixes assertion failure with new piglit
arb_draw_buffers_blend-state_set_get test.
Cc: mesa-sta...@lists.freedesktop.org
---
src/mesa/main/dlist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/main/dlist.c
On 10/16/2015 11:22 PM, Ilia Mirkin wrote:
On Fri, Oct 16, 2015 at 5:29 PM, Samuel Pitoiset
wrote:
As explained in the CUDA toolkit documentation, "a metric is a
characteristic of an application that is calculated from one or more
event values."
Signed-off-by:
On Fri, Oct 16, 2015 at 5:29 PM, Samuel Pitoiset
wrote:
> As explained in the CUDA toolkit documentation, "a metric is a
> characteristic of an application that is calculated from one or more
> event values."
>
> Signed-off-by: Samuel Pitoiset
---
src/mesa/vbo/vbo_exec_draw.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/src/mesa/vbo/vbo_exec_draw.c b/src/mesa/vbo/vbo_exec_draw.c
index 174cbc3..781991b 100644
--- a/src/mesa/vbo/vbo_exec_draw.c
+++ b/src/mesa/vbo/vbo_exec_draw.c
@@ -64,9 +64,13 @@
And remove '(void) flags' line which is not needed.
---
src/mesa/tnl/t_vb_rendertmp.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/mesa/tnl/t_vb_rendertmp.h b/src/mesa/tnl/t_vb_rendertmp.h
index 44dee76..26a1695 100644
--- a/src/mesa/tnl/t_vb_rendertmp.h
+++
When long GL_LINE_LOOP primitives don't fit in one vertex buffer they
have to be split across buffers. The code to do this was basically correct
but drivers had to pay special attention to the _mesa_prim::begin,end flags
in order to draw the sections of the line loop properly. Apparently, the
Use a new 'last_prim' pointer to simplify things.
---
src/mesa/vbo/vbo_exec_api.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/mesa/vbo/vbo_exec_api.c b/src/mesa/vbo/vbo_exec_api.c
index c1f2146..2a78eac 100644
--- a/src/mesa/vbo/vbo_exec_api.c
+++
---
src/mesa/vbo/vbo_exec_api.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/src/mesa/vbo/vbo_exec_api.c b/src/mesa/vbo/vbo_exec_api.c
index 2a78eac..903aa42 100644
--- a/src/mesa/vbo/vbo_exec_api.c
+++ b/src/mesa/vbo/vbo_exec_api.c
@@ -823,11 +823,10 @@ static void
---
src/mesa/vbo/vbo_context.h | 14 ++
src/mesa/vbo/vbo_exec_api.c | 3 +--
src/mesa/vbo/vbo_exec_draw.c | 3 +--
3 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/src/mesa/vbo/vbo_context.h b/src/mesa/vbo/vbo_context.h
index a376efe..1e85335 100644
---
---
src/mesa/vbo/vbo_exec.h | 2 --
src/mesa/vbo/vbo_exec_api.c | 3 ++-
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/mesa/vbo/vbo_exec.h b/src/mesa/vbo/vbo_exec.h
index 00378eb..a80b2c9 100644
--- a/src/mesa/vbo/vbo_exec.h
+++ b/src/mesa/vbo/vbo_exec.h
@@ -160,8 +160,6
As before, use a new 'last_prim' pointer to simplify things. Plus, add
some const qualifiers.
---
src/mesa/vbo/vbo_exec_draw.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/mesa/vbo/vbo_exec_draw.c b/src/mesa/vbo/vbo_exec_draw.c
index 781991b..412ebb6
---
src/mesa/vbo/vbo_save_api.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/mesa/vbo/vbo_save_api.c b/src/mesa/vbo/vbo_save_api.c
index fdc677f..6688ba0 100644
--- a/src/mesa/vbo/vbo_save_api.c
+++ b/src/mesa/vbo/vbo_save_api.c
@@ -330,8 +330,7 @@
On Fri, Oct 16, 2015 at 5:35 PM, Samuel Pitoiset
wrote:
>
>
> On 10/16/2015 11:22 PM, Ilia Mirkin wrote:
>>
>> On Fri, Oct 16, 2015 at 5:29 PM, Samuel Pitoiset
>> wrote:
>>>
>>> As explained in the CUDA toolkit documentation, "a metric is a
As explained in the CUDA toolkit documentation, "a metric is a
characteristic of an application that is calculated from one or more
event values."
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/Makefile.sources | 2 +
When a long GL_LINE_LOOP prim was split across primitives we drew
stray lines. See previous commit for details.
This patch converts GL_LINE_LOOP prims into GL_LINE_STRIP prims so
that drivers don't have to worry about the _mesa_prim::begin/end flags.
Bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=81174
--- Comment #16 from Brian Paul ---
I'm digging into this bug because it pertains to an issue with a particular app
and the VMware gallium driver.
The VBO code for splitting GL_LINE_LOOP is actually correct, I believe, but
On Oct 15, 2015 16:29, "Timothy Arceri" wrote:
>
> Cc: Francisco Jerez
> Cc: Jason Ekstrand
> ---
> src/glsl/nir/nir_lower_atomics.c | 22 --
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff
has_shader_storage_buffer_objects() returns true also if the OpenGL
context is 4.30 or ES 3.1.
Previously, we were saying that all atomic*() GLSL builtin functions
for SSBOs were not available when OpenGL ES 3.1 context was in use.
Fixes 48 dEQP-GLES31 tests:
Hi Brian,
On 15.10.2015 22:23, Brian Paul wrote:
> Module: Mesa
> Branch: master
> Commit: 0de5e0f3fb0f3671a3ecec6ab4473f9131ecd0ae
> URL:
> http://cgit.freedesktop.org/mesa/mesa/commit/?id=0de5e0f3fb0f3671a3ecec6ab4473f9131ecd0ae
>
> Author: Brian Paul
> Date: Wed
Otherwise there are problems when user overrides version and application
such as Piglit wants to detect used api with glGetString(GL_VERSION).
This makes it currently impossible to run glslparsertest tests for
OpenGL ES when using version override.
Below is example when using
Signed-off-by: Boyan Ding
---
src/gallium/drivers/vc4/vc4_nir_lower_blend.c | 2 +-
src/gallium/drivers/vc4/vc4_nir_lower_io.c| 4 ++--
src/gallium/drivers/vc4/vc4_program.c | 8
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Signed-off-by: Boyan Ding
---
src/gallium/drivers/freedreno/ir3/ir3_compiler_nir.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/gallium/drivers/freedreno/ir3/ir3_compiler_nir.c
b/src/gallium/drivers/freedreno/ir3/ir3_compiler_nir.c
index
On Thu, Oct 15, 2015 at 07:29:31AM -0700, Jason Ekstrand wrote:
>On Oct 14, 2015 10:48 PM, "Pohjolainen, Topi"
>wrote:
>>
>> On Wed, Oct 14, 2015 at 11:53:37AM -0700, Jason Ekstrand wrote:
>> > On Wed, Oct 14, 2015 at 1:41 AM, Pohjolainen, Topi
>
On Fri, 2015-10-16 at 09:10 +0200, Samuel Iglesias Gonsalvez wrote:
> has_shader_storage_buffer_objects() returns true also if the OpenGL
> context is 4.30 or ES 3.1.
>
> Previously, we were saying that all atomic*() GLSL builtin functions
> for SSBOs were not available when OpenGL ES 3.1 context
On Oct 15, 2015 16:14, "Connor Abbott" wrote:
>
> On Thu, Oct 15, 2015 at 6:17 PM, Kenneth Graunke
wrote:
> > Often, shader inputs/outputs are required to be aligned to vec4 slots
> > for one reason or another. When working with the scalar backend, we
Fixes following warnings:
state_tracker/st_cb_program.c: In function ‘st_new_program’:
state_tracker/st_cb_program.c:108:36: warning: passing argument 1 of
‘_mesa_init_gl_program’ from incompatible pointer type
[-Wincompatible-pointer-types]
return _mesa_init_gl_program(>Base, target, id);
On Fri, Oct 09, 2015 at 05:50:22AM -0700, Jason Ekstrand wrote:
> On Fri, Oct 9, 2015 at 12:10 AM, Pohjolainen, Topi
> wrote:
> > On Thu, Oct 08, 2015 at 05:22:47PM -0700, Jason Ekstrand wrote:
> >> This commit moves the common/modern stuff. Some legacy stuff such as
On 16/10/15 09:36, Iago Toral wrote:
> On Fri, 2015-10-16 at 09:10 +0200, Samuel Iglesias Gonsalvez wrote:
>> has_shader_storage_buffer_objects() returns true also if the OpenGL
>> context is 4.30 or ES 3.1.
>>
>> Previously, we were saying that all atomic*() GLSL builtin functions
>> for SSBOs
Reviewed-by: Tapani Pälli
On 10/16/2015 10:10 AM, Samuel Iglesias Gonsalvez wrote:
has_shader_storage_buffer_objects() returns true also if the OpenGL
context is 4.30 or ES 3.1.
Previously, we were saying that all atomic*() GLSL builtin functions
for SSBOs were not
Reviewed-by: Jason Ekstrand
On Oct 15, 2015 15:17, "Kenneth Graunke" wrote:
> VS, GS, and FS continue doing the same thing they did before. We can
> simplify the FS code a bit because it is always scalar.
>
> Compute shaders now assert that
On Oct 15, 2015 15:17, "Kenneth Graunke" wrote:
>
> The scalar VS backend has never handled float[] and vec2[] outputs
> correctly (my original code was broken). Outputs need to be padded
> out to vec4 slots.
>
> In fs_visitor::nir_setup_outputs(), we tried to process each
https://bugs.freedesktop.org/show_bug.cgi?id=92278
--- Comment #2 from Tapani Pälli ---
On quick glance at the trace it looks like one issue here is that Mesa does not
expose EXT variants for TextureParameteri and TextureParameterfv but exposing
those won't fix this as there
2015-10-16 14:36 GMT+08:00 Tapani Pälli :
> Otherwise there are problems when user overrides version and application
> such as Piglit wants to detect used api with glGetString(GL_VERSION).
>
> This makes it currently impossible to run glslparsertest tests for
> OpenGL ES
https://bugs.freedesktop.org/show_bug.cgi?id=92361
--- Comment #3 from cprigent ---
New result with last setup (Mesa 11.0.3).:
glx@glx-copy-sub-buffer Not run
glx@glx-copy-sub-buffer samples=2 Fail
glx@glx-copy-sub-buffer samples=4 Fail
glx@glx-copy-sub-buffer
---
src/mesa/main/shaderapi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/mesa/main/shaderapi.c b/src/mesa/main/shaderapi.c
index 26995ad..18e463d 100644
--- a/src/mesa/main/shaderapi.c
+++ b/src/mesa/main/shaderapi.c
@@ -713,10 +713,10 @@ get_programiv(struct
The latter holds both UBOs and SSBOs, but here we only want UBOs.
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/mesa/state_tracker/st_glsl_to_tgsi.cpp
b/src/mesa/state_tracker/st_glsl_to_tgsi.cpp
index 06f510d..f481e89
The latter holds both UBOs and SSBOs, but here we only want UBOs.
---
src/mesa/state_tracker/st_atom_constbuf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/mesa/state_tracker/st_atom_constbuf.c
b/src/mesa/state_tracker/st_atom_constbuf.c
index 69e26cb..acaa85d
This is the only place in the driver where we use this. Since we now work
with separate index spaces, always use NumUniformBlocks and
NumShaderStorageBlocks instead of NumBufferInterfaceBlocks to be more
consistent with the rest of the code.
---
src/mesa/drivers/dri/i965/brw_wm_surface_state.c |
On Fri, 2015-10-16 at 09:36 +0300, Tapani Pälli wrote:
> Otherwise there are problems when user overrides version and application
> such as Piglit wants to detect used api with glGetString(GL_VERSION).
>
> This makes it currently impossible to run glslparsertest tests for
> OpenGL ES when using
Now that we have separate index spaces for UBOs and SSBOs we do not need
to iterate through BufferInterfaceBlocks any more, we can just take the
UBO count directly from NumUniformBlocks.
---
src/mesa/main/shaderapi.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git
On Wed, 2015-10-14 at 21:40 +0300, Francisco Jerez wrote:
> Jordan Justen writes:
>
> > On 2015-10-13 22:49:08, Iago Toral wrote:
> >> On Tue, 2015-10-13 at 09:44 -0700, Jordan Justen wrote:
> >> > On 2015-10-13 05:17:37, Francisco Jerez wrote:
> >> > > Iago Toral
Tested-by: Tapani Pälli
On 10/16/2015 12:01 AM, Ian Romanick wrote:
From: Ian Romanick
Previously we could create a renderbuffer with format
MESA_FORMAT_R8G8B8A8_UNORM, convert that renderbuffer to an EGLImage,
then FAIL to convert the
On Fri, Oct 16, 2015 at 12:09:52AM +0100, Emil Velikov wrote:
> Hi Christian,
>
> I'm glad to see Thierry's work revived. Hopefully this will soon be
> the basis of many more drivers.
>
> On 11 October 2015 at 16:09, Christian Gmeiner
> wrote:
> > This commit adds a
Hi Christian,
First off, thanks for reviving this effort. It's been one of the things
that I've had nagging at me for much too long and I think it needs to be
solved. So I'm hopeful that the more people we get looking at this the
more likely it will be to come up with a solution that works well
On 10/16/2015 01:16 AM, Boyan Ding wrote:
Fixes following warnings:
state_tracker/st_cb_program.c: In function ‘st_new_program’:
state_tracker/st_cb_program.c:108:36: warning: passing argument 1 of
‘_mesa_init_gl_program’ from incompatible pointer type
[-Wincompatible-pointer-types]
On 10/16/2015 08:17 AM, Brian Paul wrote:
On 10/16/2015 12:36 AM, Michel Dänzer wrote:
Hi Brian,
On 15.10.2015 22:23, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: 0de5e0f3fb0f3671a3ecec6ab4473f9131ecd0ae
URL:
Topi,
Seeing as you're on a roll reviewing my move-the-code patches, mind one more?
--Jason
On Thu, Oct 15, 2015 at 12:06 PM, Jason Ekstrand wrote:
> This patch applies on top of my previous series to shuffle a bunch of
> the compiler code around.
>
> On Thu, Oct 15, 2015
On Fri, Oct 16, 2015 at 12:35 AM, Pohjolainen, Topi
wrote:
> On Fri, Oct 09, 2015 at 05:50:22AM -0700, Jason Ekstrand wrote:
>> On Fri, Oct 9, 2015 at 12:10 AM, Pohjolainen, Topi
>> wrote:
>> > On Thu, Oct 08, 2015 at 05:22:47PM -0700,
From: Indrajit Das
Reviewed-by: Christian König
---
src/gallium/state_trackers/va/image.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/gallium/state_trackers/va/image.c
From: Indrajit Das
Reviewed-by: Christian König
---
src/gallium/state_trackers/va/image.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/state_trackers/va/image.c
b/src/gallium/state_trackers/va/image.c
On 10/16/2015 12:36 AM, Michel Dänzer wrote:
Hi Brian,
On 15.10.2015 22:23, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: 0de5e0f3fb0f3671a3ecec6ab4473f9131ecd0ae
URL:
Hi guys,
Out of curiosity - do you know off-hand about any users of IYUV/I420 ?
I was under the impression that everyone is doing nv12/nv21/yv12 in
99% of the cases.
On 16 October 2015 at 15:53, Christian König wrote:
> From: Indrajit Das
>
On 16 October 2015 at 15:53, Christian König wrote:
> From: Indrajit Das
>
> Reviewed-by: Christian König
Nicely spotted !
For the future use correct prefix for the summary ("st/va:" here, but
git log will show you
Inspired from
http://cgit.freedesktop.org/vaapi/intel-driver/tree/src/i965_drv_video.c
Signed-off-by: Julien Isorce
---
src/gallium/state_trackers/va/context.c| 5 +-
src/gallium/state_trackers/va/surface.c| 288 -
This patch serie adds initial support for Video Post Processing.
It also implements VaCreateSurfaces2 for common purpose and
also to import a dmabuf.
Finally it adds support for headless mode, i.e. using DRM
instead of X11 for device setup.
Julien Isorce (7):
nvc0: fix crash when
On Tue 13 Oct 2015, Ben Widawsky wrote:
> There is nothing wrong with the code today, but as one modifies the code it
> turns out to be not too difficult to mess up the code, and this easy assertion
> should catch such driver implementation failures quickly.
>
> Cc: Kristian Høgsberg
If formats are not the same it seems to re-create the video
buffer with the right format.
But if the creation of this new video buffer fails the surface
loose its video buffer.
Let's just destroy the previous buffer on success.
Signed-off-by: Julien Isorce
---
Also add RGBA, RGBX and BGRX.
Also extend ChromaToPipe and implement PipeToYCbCr.
Note that gstreamer-vaapi check all the VAImageFormat fields.
Signed-off-by: Julien Isorce
---
src/gallium/state_trackers/va/image.c | 10 ++--
On Fri, Oct 16, 2015 at 6:13 PM, Julien Isorce wrote:
>
>
> On 18 September 2015 at 21:34, Ilia Mirkin wrote:
>>
>> On Fri, Sep 18, 2015 at 4:29 PM, Julien Isorce
>> wrote:
>> >
>> >
>> > On 17 September 2015 at 17:52, Ilia
On 10/16/2015 04:14 PM, Matt Turner wrote:
On Fri, Oct 16, 2015 at 2:25 PM, Brian Paul wrote:
And remove '(void) flags' line which is not needed.
---
src/mesa/tnl/t_vb_rendertmp.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
On 10/16/2015 04:11 PM, Jose Fonseca wrote:
On 15/10/15 20:01, Brian Paul wrote:
Before, if make_texture() or st_create_texture_sampler_view() failed
we silently no-op'd the glDrawPixels. Now, set GL_OUT_OF_MEMORY.
This also allows us to un-nest a bunch of code.
---
This patch allows to use gallium vaapi without requiring
a X server running for your second graphic card.
Signed-off-by: Julien Isorce
---
src/gallium/state_trackers/va/Makefile.am | 9 ++
src/gallium/state_trackers/va/context.c | 49 +++
Improve following functions to support VA_PROFILE_NONE profile (vpp):
vlVaQueryConfigProfiles
vlVaQueryConfigEntrypoints
vlVaCreateConfig
vlVaQueryConfigAttributes
Add VADriverVTableVPP and improve following functions to support vpp:
vlVaCreateContext
vlVaDestroyContext
vlVaBeginPicture
On Tue 13 Oct 2015, Ben Widawsky wrote:
> The allocate_surface_state already zeroes out the surface state, and doing it
> later in the function is destructive for what we want to accomplish when we
> split out support for gen9 fast clears (next patch).
>
> NOTE: Only dword 12 actually needed to
For now it is limited to RGBA, BGRA, RGBX, BGRX surfaces.
Signed-off-by: Julien Isorce
---
src/gallium/state_trackers/va/surface.c| 90 +-
src/gallium/state_trackers/va/va_private.h | 1 +
2 files changed, 90 insertions(+), 1 deletion(-)
Signed-off-by: Julien Isorce
---
src/gallium/drivers/nouveau/nvc0/nvc0_resource.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_resource.c
b/src/gallium/drivers/nouveau/nvc0/nvc0_resource.c
index
On 16/10/15 23:24, Brian Paul wrote:
Before, if make_texture() or st_create_texture_sampler_view() failed
we silently no-op'd the glDrawPixels. Now, set GL_OUT_OF_MEMORY.
This also allows us to un-nest a bunch of code.
v2: also check if allocation of sv[1] fails, per Jose.
---
On 15/10/15 20:01, Brian Paul wrote:
If we didn't find a gallium surface format that exactly matched the
glDrawPixels format/type combination, we used some other 32-bit packed
RGBA format and swizzled the whole image in the mesa texstore/format code.
That slow path can be avoided in some common
But this patch doesn't enable fast clears! The reverts in pathches 6 and
7 need to be folded into this patch, otherwise the patch does not do
what it claims.
Also, you can't enable fast clears before patches 4 and 5 without introducing
regressions. Patches 4 and 5 must precede this patch.
On Tue
On 15/10/15 20:01, Brian Paul wrote:
Before, if make_texture() or st_create_texture_sampler_view() failed
we silently no-op'd the glDrawPixels. Now, set GL_OUT_OF_MEMORY.
This also allows us to un-nest a bunch of code.
---
src/mesa/state_tracker/st_cb_drawpixels.c | 74
On 18 September 2015 at 21:34, Ilia Mirkin wrote:
> On Fri, Sep 18, 2015 at 4:29 PM, Julien Isorce
> wrote:
> >
> >
> > On 17 September 2015 at 17:52, Ilia Mirkin wrote:
> >>
> >> On Wed, Sep 16, 2015 at 8:22 AM, Julien
Before, if make_texture() or st_create_texture_sampler_view() failed
we silently no-op'd the glDrawPixels. Now, set GL_OUT_OF_MEMORY.
This also allows us to un-nest a bunch of code.
v2: also check if allocation of sv[1] fails, per Jose.
---
src/mesa/state_tracker/st_cb_drawpixels.c | 76
Supported on R700 and up.
Signed-off-by: Glenn Kennard
---
Not exactly a commonly used extension, but might as well set the
hardware registers rather than just dropping the hint on the floor.
src/gallium/drivers/r600/evergreen_state.c | 13 +
Reviewed-by: Sinclair Yeh
On Thu, Oct 15, 2015 at 01:01:42PM -0600, Brian Paul wrote:
> So that we can use it directly from the mesa/gallium state tracker.
> ---
> src/mesa/main/texstore.c | 40
> src/mesa/main/texstore.h | 11
1 - 100 of 113 matches
Mail list logo