Commits (82)
-
Mike Blumenkrantz authoredReviewed-by:
Dave Airlie <airlied@redhat.com> Part-of: <!11836>
ba3c4ce3 -
Mike Blumenkrantz authored
Reviewed-by:
d5dd1259 -
Mike Blumenkrantz authored
there's a screen limit for vertex buffer offsets (???), so if a buffer is going to overflow that limit, just rebind it as a new tmp buffer and clamp the offset to 0 this also applies to buffer rebinds Reviewed-by:
9823b970 -
Mike Blumenkrantz authored
the batch state counting belongs in the flush call, and draws/computes should each just check their counts and flush directly Reviewed-by:
49ee703e -
Mike Blumenkrantz authored
Reviewed-by:
1ffe73c7 -
Mike Blumenkrantz authored
Reviewed-by:
2795537d -
Mike Blumenkrantz authored
Reviewed-by:
10e7cb58 -
Mike Blumenkrantz authored
Reviewed-by:
e7f958d8 -
Mike Blumenkrantz authored
need this to avoid deadlocks Reviewed-by:
0dc77c8a -
Mike Blumenkrantz authored
tracking mem usage on the context is bad because if an app is always using a large amount of memory across multiple batches, it triggers the oom flushes on every flush and forces fencing instead, add an explicit flag for oom flushing and another for stalling, then flag oom flushing and stalling as needed, with set_framebuffer_state being an additional flush point now since it's guaranteed not to split renderpasses also proactively prune pending batch states if there's a lot of them Reviewed-by:
d8905446 -
Mike Blumenkrantz authored
no functional changes Reviewed-by:
fdfa155f -
Mike Blumenkrantz authored
Reviewed-by:
7aca74e2 -
Mike Blumenkrantz authored
Reviewed-by:
2736bf4e -
Mike Blumenkrantz authored
Reviewed-by:
559e009a -
Mike Blumenkrantz authored
Reviewed-by:
849c5208 -
Mike Blumenkrantz authored
do set allocation when getting pool, queue filled pools for delete Reviewed-by:
8db2d534 -
Mike Blumenkrantz authored
the number of allocated sets should be directly compared to the maximum Reviewed-by:
e42bb25e -
Daniel Stone authoredThis reverts commit 1f4ff4ed. Part-of: <!12016>
d8bfad70 -
Dave Airlie authored
It turns out for QBO you really need to explicitly support time elapsed queries to avoid wierd interactions with the non-qbo query paths. Fixes: 506e51b8 ("llvmpipe: initial query buffer object support. (v2)") Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> Part-of: <!11946>
2f5cd08e -
Timothy Arceri authored
Unfortunately I contacted the dev about this issue years ago and he made a fix, but it has never been released after all these years. This stops the screen from being completely black in game. CC: mesa-stable Reviewed-by:
Marek Olšák <marek.olsak@amd.com> Part-of: <!11941>
f3ec4a93 -
Based-on: https://patchwork.freedesktop.org/patch/445672/?series=92870&rev=1 Signed-off-by:
Rob Clark <robdclark@chromium.org> Part-of: <!12021>
215adc2f -
Rhys Perry authoredSigned-off-by:
Rhys Perry <pendingchaos02@gmail.com>
Reviewed-by: Daniel Schürmann <daniel@schuermann.dev> Closes: #5105 Cc: mesa-stable Part-of: <!12004>
211d1dfd -
Juan A. Suárez authored
Signed-off-by:
Juan A. Suarez Romero <jasuarez@igalia.com> Part-of: <!12020>
a45117a3 -
Simon Ser authored
Taken from EGL-Registry commit dc0b58dca533c5882c38bc623d133190fff883a4. Signed-off-by:
Simon Ser <contact@emersion.fr> Acked-by:
Emil Velikov <emil.l.velikov@collabora.com> Part-of: <!11797>
1b96c4e2 -
Simon Ser authored
This new EGL extension has been introduced in [1]. When we have a DRM device and a render node, we can advertise the extension and return the render node name for the EGL_DRM_RENDER_NODE_FILE_EXT query. For the special software EGL device, we can advertise the extension and return NULL for the EGL_DRM_RENDER_NODE_FILE_EXT query, because we can guarantee that llvmpipe will never use a render node for rendering operations. However, llvmpipe might be using a primary node when used with the GBM platform. So we can't advertise EXT_device_drm in this case. When we have a DRM device but no render node, that means we're on a split render/display SoC. We _should_ return the render node used by the renderonly driver, however Mesa needs more plumbing to allow this, so let's just disable the extension for now. [1]: https://github.com/KhronosGroup/EGL-Registry/pull/127 Signed-off-by:
Emil Velikov <emil.l.velikov@gmail.com> Part-of: <!11797>
2a860bb8 -
Kai Wasserbäch authoredWe need it in the next commit to replace setting the stack alignment on i386 with LLVM >= 13 through the TargetOption::StackAlignmentOverride, which was removed in the upstream commit <https://github.com/llvm/llvm-project/commit/3787ee457173c3612aac4c9b1a2b6d6ab0202616 >. Unfortunately Module::setOverrideStackAlignment() is not available through the C API and we need to wrap it ourselves. Signed-off-by:
Kai Wasserbäch <kai@dev.carbon-project.org>
Reference: #4906
Reviewed-by: Roland Scheidegger <sroland@vmware.com> Part-of: <!11940>
c1b4c64a -
Kai Wasserbäch authored
Use the newly added wrapper lp_set_module_stack_alignment_override() to achieve the same end result. Signed-off-by:
Kai Wasserbäch <kai@dev.carbon-project.org>
Closes: #4906
Reviewed-by: 3a2d317b -
Alyssa Rosenzweig authored...even if neither GL or VK drivers are being built. Useful for building the standalone compiler on non-Linux systems. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>c10b8866 -
Alyssa Rosenzweig authored
These dependencies are not necessarily portbale, but bifrost_compiler itself is. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>55e6dd37 -
Alyssa Rosenzweig authored
It's not needed for the standalone compiler. These depend on xf86drm.h which is not available on other platforms where we might want to build the standalone compiler. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>a95dd949 -
Alyssa Rosenzweig authored
The enums alias. Fixes the following warning under clang: ../src/panfrost/bifrost/bifrost_compile.c:2515:25: warning: implicit conversion from enumeration type 'enum bifrost_texture_fetch' to different enumeration type 'enum bifrost_lod_mode' [-Wenum-conversion] BIFROST_TEXTURE_FETCH_TEXEL; Signed-off-by:Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>b56f5c27 -
Alyssa Rosenzweig authored
Fixes the warning caught by clang (why did gcc miss this one?) ../src/panfrost/bifrost/bifrost_compile.h:81:45: warning: initializer overrides prior initialization of this subobject [-Winitializer-overrides] .lower_bitfield_extract_to_shifts = true, Signed-off-by:Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>7346ab85 -
Alyssa Rosenzweig authored
Fixes warnings like the following under clang: src/panfrost/bifrost/bi_printer.c:599:1: warning: unused function 'bi_widen_as_str' [-Wunused-function] bi_widen_as_str(enum bi_widen widen) Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Part-of: <!12003>1d6c790f -
Jason Ekstrand authoredReviewed-by:
Emma Anholt <emma@anholt.net> Part-of: <!12005>
c6102dda -
Jason Ekstrand authored
Several bits of hardware require the division by 6 to happen in the shader. May as well have common lowering for it. Reviewed-by:
60b5faf5 -
Jason Ekstrand authored
No point in carrying all this code around twice each in two back-ends. Reviewed-by:
Rhys Perry <pendingchaos02@gmail.com>
Part-of: <mesa/mesa!12005>e83fe65c -
Jason Ekstrand authored
Reviewed-by:
17f7b4b8 -
Dave Airlie authored
For compute shaders stats avail was never signalling because nothing flushed. Fixes dEQP-VK.query_pool.statistics_query.host_query_reset.compute_shader_invocations.64bits_cmdcopyquerypoolresults_primary and others Reviewed-by:
e8fce38e -
Dave Airlie authored
VK CTS has a test that does -256 for sample index but since we use signed >= we fail and write to random memory, changing to uint here for comparisons for out of bounds and address calcs should ensure, we stay within bounds even for negative vals. Remove unused int_type/bld while here. Fixes dEQP-VK.texture.multisample.invalid_sample_index.sample_count_4 Reviewed-by:
1087cf68 -
Jason Ekstrand authored
Reviewed-by:
Jordan Justen <jordan.l.justen@intel.com> Part-of: <mesa/mesa!11991>
92955877 -
Emma Anholt authored
glsl_to_tgsi had been emitting outputs in sorted order, and it seems virgl has a dependency on that -- it collects outputs into an array and indexes by the subtracting the ".First" value of the first one seen, even if that's not the first entry in the array. Fixes the regressions in deqp-gles2 on virgl with ST_DEBUG=force_nir, and fixes neverball trace rendering. Reviewed-by:
af0fa501 -
Emma Anholt authored
Hopefully this fixes the flakes that have happened since the suballoc changes. Fixes: 737d4caa ("freedreno: Suballocate our long-lived ring objects.") Part-of: <mesa/mesa!12002>
b1dbbc3d -
Alyssa Rosenzweig authored
Tells you how much use Mali T720 gets that nobody noticed but Icecream95... Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reported-by: Icecream95 <ixn@disroot.org> Acked-by:
11cb374a -
Sagar Ghuge authored
CoverityID: 1487496 Fixes: cde9ca61 "intel/compiler: Make decision based on source type instead of opcode" Signed-off-by:
Sagar Ghuge <sagar.ghuge@intel.com> Reviewed-by:
Marcin Ślusarz <marcin.slusarz@intel.com>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com> Part-of: <!11985>
0608e76e -
Sagar Ghuge authored
We need to lower the add3 instruction simd width otherwise in simd32 mode, we endup writing 4 register wide data which is not allowed. Reported-by:
ef29bb6b -
Dave Airlie authored
I was trying to fix this test, but noticed brw_clip.c in i965 does a * 2 here, and it seems to fix this test as well. Fixes: dEQP-GLES2.functional.polygon_offset.default_displacement_with_units Fixes: f9e2c243 ("draw,llvmpipe,util: add depth bias calculation for arb_depth_buffer_float") Reviewed-by:
1e5a470b -
Timothy Arceri authored
This expands on commit c54c4232. See the code comment for full justifications. At the time of the previous commit Ian wanted to limit the relaxing of the rule to GLSL 3.30 as that was the highest version of shaders seen in the wild that were having trouble with the stricter rules. However since then I've found that the long standing issue with tess shaders failing to compile in the game 'Layers Of Fear' is due to this same issue. The game uses 4.10 shaders and also makes use of explicit varying locations, so here we relax the rule to 4.20 and make sure to apply the restriction to shaders using varyings with explicit locations also. Fixes: c54c4232 ("glsl: relax rule on varying matching for shaders older than 4.00") Reviewed-by:
Samuel Iglesias Gonsálvez <siglesias@igalia.com>
Reviewed-by: Matt Turner <mattst88@gmail.com> Part-of: <mesa/mesa!11873>
0e0633ca -
Alyssa Rosenzweig authored
Required to build Mesa on macOS with -Dbuild-tests=true -Dglx=gallium-xlib Without this change, the build fails with In file included from ../src/gallium/targets/graw-xlib/graw_xlib.c:8: ../src/gallium/include/frontend/xlibsw_api.h:5:10: fatal error: 'X11/Xlib.h' file not found #include <X11/Xlib.h> With `brew sh` X11 is found but linking fails due to `llvm-ar` missing in the path. That issue appears to be unrelated to this missing dependency. X11 is installed via XQuartz, so Homebrew should not be required. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 061508d3 -
Juan A. Suárez authored
Switch from using debug_control structure to debug_named_value structure. The main nice feature is that it provides a "help" option, so using "V3D_DEBUG=help" will print all the debug options with a brief description. Useful to avoid going to https://docs.mesa3d.org/envvars.html everytime we need to know the available options. v1: - Modify a couple of debug option documentation (Alejandro) Reviewed-by:
Alejandro Piñeiro <apinheiro@igalia.com>
Signed-off-by: 82d84a35 -
Jason Ekstrand authored
It's an intel-specific opcode and will never come through TGSI. Reviewed-by:
Adam Jackson <ajax@redhat.com> Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: Connor Abbott <cwabbott0@gmail.com> Part-of: <!11775>
a2332d96 -
Jason Ekstrand authored
It's an intel-specific texture source and will never be seen on AMD. Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: a7b429e8 -
Jason Ekstrand authored
It's an intel-specific opcode and will never be seen on panfrost Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: cdde108a -
Jason Ekstrand authored
It's intel-specific, used to get at MSAA compression information. Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 4465ca29 -
Jason Ekstrand authored
Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: fa717a20 -
Jason Ekstrand authored
We set an explicit LOD immediately afterwards so we don't want implicit mipmap selection. Reviewed-by:
7ecfbaf7 -
Alyssa Rosenzweig authored
As discussed with Jason and Connor, this is probably subtly broken on Mali T720. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: f9442e46 -
Jason Ekstrand authored
Only fragment and some compute shaders support implicit derivatives. They're totally meaningless without helper invocations and some understanding of the dispatch pattern. We've got code to lower nir_texop_tex in these shader stages to use an explicit derivative of 0 but it was pretty badly broken: 1. It only handled nir_texop_tex, not nir_texop_txb or nir_texop_lod. 2. It didn't take min_lod into account 3. It was conflated with adding a missing LOD parameter to opcodes which expect one such as nir_texop_txf. While not really a bug, this does make it way harder to reason about the code. 4. Unless you set a flag (which most drivers don't), it left the opcode nir_texop_tex instead of nir_texop_txl which it should have been. This reworks it to go through roughly the same path as other LOD lowering only with a constant lod of 0 instead of calling out to nir_texop_lod. We also get rid of the lower_tex_without_implicit_lod flag because most drivers set it and those that don't are probably subtly broken. If someone really wants to get nir_texop_tex in their vertex shaders, they can write a new patch to add the flag back in. Fixes: e382890e "nir: set default lod to texture opcodes that..." Fixes: d5ac5d6e "nir: Add option to lower tex to txl when..." Reviewed-by:74ec2b12 -
Erik Faye-Lund authoredReviewed-by:
Jason Ekstrand <jason@jlekstrand.net>
Reviewed-by: e212a191 -
Mike Blumenkrantz authored
Reviewed-by:
Jason Ekstrand <jason@jlekstrand.net>
Reviewed-by: Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 499cc7a9 -
Jason Ekstrand authored
Reviewed-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Acked-by: 1431f6c7 -
Ryan Neph authored
virglrenderer doesn't support null-terminated message strings, so there's no reason for the guest to allow it. Signed-off-by:
Ryan Neph <ryanneph@google.com> Reviewed-by:
Chia-I Wu <olvaffe@gmail.com> Part-of: <mesa/mesa!12043>
0972b0f7 -
Adam Jackson authored
We started doing this in: commit 4d6d55de Author: Tapani Pälli <tapani.palli@intel.com> Date: Mon Sep 26 10:03:32 2016 +0300 egl: stop claiming support for pbuffer + msaa This fixes a crash in egl-create-msaa-pbuffer-surface Piglit test and same crash in many dEQP EGL tests. Whatever bug that was papering over appears to be fixed by now, I can no longer reproduce that crash with piglit. Furthermore, disabling that bit in the generic dri2 code had the side effect that the surfaceless platform would advertise EGLConfigs with _no_ supported surface types (since surfaceless only supports pbuffers). Reviewed-by:18e7633b -
Emma Anholt authored
We've had issues with these before when merging to Chrome OS, so let's make sure we're testing them now that we can do surfaceless pbuffer MSAA. Reviewed-by:
366de834 -
Alyssa Rosenzweig authored
Now there's only a single genx entrypoint. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com> Part-of: <mesa/mesa!11851>
d0e6db10 -
Alyssa Rosenzweig authored
Move it up in the file to avoid forward decls. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 5039c66a -
Alyssa Rosenzweig authored
Arch-independent. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 4cce6b91 -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 284b71a2 -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 2670c4db -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: fd298985 -
Alyssa Rosenzweig authored
Midgard calls this nearest but Bifrost calls it point sample. Of the two, nearest is the standard term, so change the Bifrost XML to use that name. That way we can share more code constructing samplers. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: c80732ea -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 84c33f18 -
Alyssa Rosenzweig authored
Midgard code is basically a subset of the Bifrost/Valhall code. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 433ca313 -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: a222ead4 -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: f4b0d173 -
Alyssa Rosenzweig authored
This is safer, since it allows the thing being concatenated to itself be an expande macro, which we'll use as a stopgap to construct tiler jobs with unified code. It's also a bit more readable, I think. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: d7a0720e -
Alyssa Rosenzweig authored
Mostly trivial substitutions to get rid of dev->arch, dev->quirks, and pan_is_bifrost() Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 3d0f6592 -
Alyssa Rosenzweig authored
Secretly depends on GenXML. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 6f0c235d -
Alyssa Rosenzweig authored
Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Reviewed-by: 058d4d3b -
Alyssa Rosenzweig authored
The logic was incorrectly inverted, although it is correct for Midgard and in OpenGL. Signed-off-by:
Alyssa Rosenzweig <alyssa@collabora.com>
Suggested-by: b17f90ab -
Georg Lehmann authored
Signed-off-by:
Georg Lehmann <dadschoorse@gmail.com> Reviewed-by:
Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> Part-of: <!11610>
c6bcafcc -
Georg Lehmann authored
Signed-off-by:
890b1c0f -
Chia-I Wu authored
venus only needs to know if a WSI image is a prime blit source. In an upcoming swapchain image rework, the prime blit destination is unknown when the WSI image is created. Replace prime_blit_buffer by a bool. Signed-off-by:
Jason Ekstrand <jason@jlekstrand.net>
Part-of: <!12046>bd9550b0
docs/nir/tex.rst
0 → 100644