aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-02-15docs: add sha256sum for 23.3.6upstream-23.3Eric Engestrom
2024-02-15VERSION: bump for 23.3.6upstream-mesa-23.3.6Eric Engestrom
2024-02-15docs: add release notes for 23.3.6Eric Engestrom
2024-02-15nir/lower_io: fix handling for compact arrays with indirect derefsMike Blumenkrantz
this logic relies on constant indexing for compact arrays, but this is frequently not the case for compact array builtins (e.g., gl_TessLevelOuter). the usual strategy of lowering to temps isn't viable in TCS, which means io lowering has to be able to handle indirect access to these builtins without crashing cc: mesa-stable Reviewed-by: Dave Airlie <airlied@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27534> (cherry picked from commit 9e2c7314f2867de6f43e2add992590cfb92ccddd)
2024-02-15intel: Fix intel_get_mesh_urb_config()José Roberto de Souza
The round up in 'next_address_8kb = DIV_ROUND_UP(push_constant_kb, 8)' was not decreasing the amount of URB available for Mesh and Task, what could cause an over allocation of URB. There was also no minimum entries enforcement for Mesh and Task, what could cause 0 r.mesh_entries to be set in a case where tue_size_dw is 90% > than mue_size_dw. Same for r.task_entries when Task is enabled. Also adding a few more asserts to help debug. This fixes at least dEQP-VK.mesh_shader.ext.properties.mesh_payload_size in LNL but it has potential to fixes other Mesh tests as well. Cc: mesa-stable Signed-off-by: José Roberto de Souza <jose.souza@intel.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27555> (cherry picked from commit d0fba810b3d334191ead4f16f5ba786250a70c32)
2024-02-15aco/gfx11+: limit hard clauses to 32 instructionsGeorg Lehmann
https://github.com/llvm/llvm-project/pull/81287 Foz-DB Navi31: Totals from 406 (0.52% of 78112) affected shaders: Instrs: 585342 -> 585750 (+0.07%) CodeSize: 3077856 -> 3079456 (+0.05%); split: -0.00%, +0.05% Latency: 3263165 -> 3263326 (+0.00%); split: -0.00%, +0.01% InvThroughput: 664092 -> 664114 (+0.00%); split: -0.00%, +0.00% VClause: 11143 -> 11537 (+3.54%) SClause: 11878 -> 11884 (+0.05%) Copies: 39807 -> 39815 (+0.02%) Cc: mesa-stable Reviewed-by: Rhys Perry <pendingchaos02@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27569> (cherry picked from commit 6121497228d7388a5711c9458945b5903c401c7e)
2024-02-15nir/lower_cl_images: record image_buffers and msaa_imagesKarol Herbst
Cc: mesa-stable Signed-off-by: Karol Herbst <kherbst@redhat.com> Reviewed-by: Jesse Natalie <jenatali@microsoft.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27385> (cherry picked from commit 727cddd338aceb48915725fefec3fcc563e956e1)
2024-02-15radv,driconf: Enable active AS leaf workaround for Jedi SurvivorFriedrich Vock
Another game that can't get AS updates right. Cc: mesa-stable Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27590> (cherry picked from commit afab80bdb69928a6a5724a813b0903d0fdc62f8f)
2024-02-15llvmpipe: Set "+64bit" for X86_64Lepton Wu
Without this, on some "buggy" qemu cpu setup, LLVM could crash if LLVM detects the wrong CPU type. Fixes: f92cadccc65 ("llvmpipe: Always using util_get_cpu_caps to get cpu caps for llvm on x86") Signed-off-by: Lepton Wu <lepton@chromium.org> Reviewed-by: Yonggang Luo <luoyonggang@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27539> (cherry picked from commit 04d26ceb0a87ca9e05a00405e2544f256e8e046c)
2024-02-15Revert "zink: always force flushes when originating from api frontend"Konstantin Seurer
This reverts commit 03f049f49730b8b1268f2975fc34ac2b1f9a4ef9. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27560> (cherry picked from commit 097e543c0a061382e07063705225304eefff6d1f)
2024-02-15zink: Always set mfence->submit_count to the fence submit_countKonstantin Seurer
Fixes glFinish not finishing all GPU work. cc: mesa-stable Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8257 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27560> (cherry picked from commit aed5e4e1f2bcbad5a63d483cf97bf7c30ca9cccc)
2024-02-15radeonsi/vcn: Don't reinitialize encode session on bitrate/fps changeDavid Rosca
When bitrate or fps change is detected, only update rate control parameters instead of completely reinitializing encode session. This fixes an issue where if application changed bitrate or fps often, the output bitrate would significantly overshoot the target bitrate in some cases. In other cases, the output bitrate would be extremely low instead. Cc: mesa-stable Reviewed-by: Ruijing Dong <ruijing.dong@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27548> (cherry picked from commit 8d44a115080645c210e055fa410fb18accf510aa)
2024-02-14radv: fix RGP barrier reason for RP barriers inserted by the runtimeSamuel Pitoiset
Without that, RGP is confused and it's reporting CmdPipelineBarrier() instead of CmdRenderPassSync(). Cc: mesa-stable Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27546> (cherry picked from commit b58de424f41ffcdd2c997276c7d20a659e10c272)
2024-02-14vulkan/runtime: add helper to query attachment layoutLionel Landwerlin
The runtime is turning GENERAL layouts into FEEDBACK_LOOP ones when it detects feedback loops in a render pass. This is breaking drivers that would like to use a different HW layout for those 2 layouts because if the application inserts barrier in the render pass, the barriers the driver sees are inconsistent. This could lead to barrier of this type : - GENERAL -> FEEDBACK_LOOP (runtime) - GENERAL -> GENERAL (app) - FEEDBACK_LOOP -> GENERAL (runtime) Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Reviewed-by: Ivan Briano <ivan.briano@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23523> (cherry picked from commit 76cf391255df07e8a2f0ffcdea74707baba8587a)
2024-02-14nvk: Don't clobber vb0 after repeated blitsM Henning
If a program does two blits in a row, we internally do a sequence of operations that involves binding vb0. Previously, the vb0 state after each operation would look something like: | operation | cmd->state.gfx.vb0 | hardware | save->vb0 | | ---------------------------- | ------------------ | --------- | --------- | | | user | user | | | nvk_meta_begin() | user | user | user | | BindVertexBuffers(internal0) | internal0 | internal0 | user | | nvk_meta_end() | internal0 | user | | | nvk_meta_begin() | internal0 | user | internal0 | | BindVertexBuffers(internal1) | internal1 | internal1 | internal0 | | nvk_meta_end() | internal1 | internal0 | | That is, CmdBindVertexBuffers() would update cmd->state.gfx.vb0, but nvk_meta_end() would not. This meant that the last operation would bind a driver-internal buffer instead of the original value that the user set. This change fixes the issue by tracking cmd->state.gfx.vb0 in nvk_cmd_bind_vertex_buffer(), which both CmdBindVertexBuffers() and nvk_meta_end() call into. After this commit, the state looks like: | operation | cmd->state.gfx.vb0 | hardware | save->vb0 | | ---------------------------- | ------------------ | --------- | --------- | | | user | user | | | nvk_meta_begin() | user | user | user | | BindVertexBuffers(internal0) | internal0 | internal0 | user | | nvk_meta_end() | user | user | | | nvk_meta_begin() | user | user | user | | BindVertexBuffers(internal1) | internal1 | internal1 | user | | nvk_meta_end() | user | user | | To test this commit, build gtk4 commit 87b66de1, run: GSK_RENDERER=vulkan gtk4-demo --run=image_scaling then select trilinear filtering in the dropdown and check for rendering artifacts. Fixes: e1c66501 ("nvk: Use vk_meta for CmdClearAttachments") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27559> (cherry picked from commit d98ff2cc4add875f2e372bf69e45b1c6a7b8a9c6)
2024-02-14aco: don't remove branches that skip v_writelane_b32Georg Lehmann
Cc: mesa-stable Reviewed-by: Daniel Schürmann <daniel@schuermann.dev> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27537> (cherry picked from commit cd6d9c5918feabe18a58f6b1096a55c1970d0883)
2024-02-14aco/gfx11+: disable v_pk_fmac_f16_dppGeorg Lehmann
Public docs are apparently wrong: https://github.com/llvm/llvm-project/pull/79598#issuecomment-1933988048 Cc: mesa-stable Reviewed-by: Daniel Schürmann <daniel@schuermann.dev> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27533> (cherry picked from commit e927c5004f9f6305e2269b1b1f0950bcba916ce7)
2024-02-14Revert "ci: Enable GALLIUM_DUMP_CPU=true only in the clang job"Timothy Arceri
Rob worded it well in 9e8450b65ccc. "We don't want util_cpu to vomit cpu caps all over the test output." This reverts commit c6979d97e46907ff341665200b853cbca1d5524c. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27564> (cherry picked from commit 62fa5c8d0f059ba75d7208a0d081da811065ba1c)
2024-02-14hasvk: add missing linker argumentsMark Janes
vulkan_icd_link_args was added for other vulkan drivers but not hasvk. Without it, statically linked json-c symbols are wrongly exported. Ref: 2b1e9b0fd69 ("anv: add linker script to fix android symbols") Fixes: 78578a6ddb4 ("vk: move radv's linker symbols scripts for use in all drivers") Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27540> (cherry picked from commit fb7240bef96b9faef6eba3a35205567dad1ec343)
2024-02-14zink: adjust swizzled deref loads by the variable component offsetMike Blumenkrantz
this code is intended to transform a block like: ``` 32 %306 = @load_interpolated_input (%34, %0 (0x0)) (base=3, component=2, dest_type=float32, io location=VARYING_SLOT_VAR3 slots=1) 32x2 %307 = fsub %305, %306.xx ``` into derefs. the existing code generates this: ``` decl_var shader_in INTERP_MODE_NONE none vec2 #7 (VARYING_SLOT_VAR3.zw, 0, 0) 32 %516 = deref_var &#7 (shader_in vec2) 32x2 %517 = @load_deref (%516) (access=none) 32 %518 = mov %517.z error: src->swizzle[i] < num_components (../src/compiler/nir/nir_validate.c:216) ``` the problem is attempting to reapply the component offset to a variable which is already at an offset fixes #10567 Fixes: 17a35412dcc ("zink: re-rework i/o variable handling to make having variables entirely optional") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27522> (cherry picked from commit 0a243a7241e26292ca55a97f5f8d464001b532cd)
2024-02-14mesa: plumb errors through to texture allocationMike Blumenkrantz
the spec allows this and tests like spec@arb_texture_multisample@arb_texture_multisample-dsa-texelfetch expect it cc: mesa-stable Reviewed-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25931> (cherry picked from commit fab5c706fe453f440d3c85013d24dbe8230e36cc)
2024-02-14pan/va: Add missing valhall_enums dep to valhall_disasmBoris Brezillon
valhall_disasm compilation fails if the valhall_enums.h has not be generated. Fixes: 619566dea18e ("pan/va: Generate header containing enums") Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10553 Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com> Reviewed-by: Dylan Baker <dylan@pnwbakers.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27524> (cherry picked from commit 49069a1243de8de3f658faa5fd8bb71d31c7d907)
2024-02-14panfrost: Pad compute jobs with zeros on v4Boris Brezillon
Apparently, Midgard GPUs don't like when the last 2 words of compute/vertex jobs contain garbage. Extend the compute job definition to include a padding section thus aligning the job on a 64-byte boundary, and add the according pan_section_pack() calls where we have a compute job filled. Fixes: b76420be1f1f ("panfrost: Split command stream descriptor definitions per-gen") Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10558 Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com> Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Tested-by: Anton Bambura <jenneron@postmarketos.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27515> (cherry picked from commit 5b1b76e9cdd8b44538aa327c7705381fa68b891b)
2024-02-14driconf: Apply dual color blending workaround to Dying LightSviatoslav Peleshko
The game uses shader with `location=0` and `location=1` outputs where it wants dual source blending and should've used `location=0, index=0` and `location=0, index=1`. Cc: mesa-stable Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10413 Signed-off-by: Sviatoslav Peleshko <sviatoslav.peleshko@globallogic.com> Reviewed-by: Tapani Pälli <tapani.palli@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27509> (cherry picked from commit 0a1c8779e8705737bdb69622badaf2446ff6924a)
2024-02-14driconf: Advertise GL_EXT_shader_image_load_store on iris for SVP13Kenneth Graunke
SPECviewperf creo-03 needs GL_EXT_shader_image_load_store in order for its shaders to compile but we don't support a few corner cases that didn't make it into the ARB variant. It seems to run fine with an override, so just do that for now. Cc: mesa-stable Acked-by: Tapani Pälli <tapani.palli@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27429> (cherry picked from commit 24d3c832121b123b42e3cbc39e8225085139cbb1)
2024-02-14freedreno: Fix MSAA z/s layout in GMEMRob Clark
A bit surprised that this didn't show up in any piglit or deqp. Fixes: cf0c7258ee05 ("freedreno/a5xx: MSAA") Signed-off-by: Rob Clark <robdclark@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27508> (cherry picked from commit c3062e3402fe693dd1cc0137217611081f993f12)
2024-02-14r300: fix vs output register indexingPavel Ondračka
Vertex shaders were writing TEXCOORDs before GENERICS, however fragment shaders were reading it the opposite way, so this caused problems for shaders that used both TEXCOORD and GENERIC varyings. Fixes: d4b8e8a48144f4b899d48c271558f0dc613632cb Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10489 Signed-off-by: Pavel Ondračka <pavel.ondracka@gmail.com> Reviewed-by: Filip Gawin <filip.gawin@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27469> (cherry picked from commit 0ac6801970f88402f4f98455652448bc5ca97096)
2024-02-14iris: Fix return of iris_wait_syncobj()José Roberto de Souza
iris_wait_syncobj() succeed if IOCTL return is 0 otherwise it failled. Cc: mesa-stable Signed-off-by: José Roberto de Souza <jose.souza@intel.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27500> (cherry picked from commit 138303fb9dbad7754b109ca846a17799cc0dc1d5)
2024-02-14ir3/ra: Fix bug with collect source handlingConnor Abbott
It can be the case that a collect and one of its sources are assigned to non-overlapping parts of the same merge set, for example: ssa_1 = ... ssa_2 = ... ssa_3 = ... ssa_4 = collect ssa_1, ssa_2 (kill), ssa_3 ... = ssa_4 (kill) ssa_5 = collect ssa_1, ssa_3 ... = ssa_1 (kill) ... = ssa_3 (kill) ... = ssa_5 (kill) If we merge the first collect first, we get a merge set: ssa_1 (offset 0) ssa_2 (offset 2) ssa_3 (offset 4) ssa_4 (offset 0) Now, we decide to merge ssa_1 and ssa_5: ssa_1 (offset 0) ssa_2 (offset 2) ssa_3 (offset 4) ssa_4 (offset 0) ssa_5 (offset 0) ssa_3 cannot become a child of ssa_5 in the interval tree, just like a source not in the same merge set, so we should not remove it and then reinsert it assuming that RA will make it a child of ssa_5. This fixes an RA validation error in Farming Simulater. Fixes: 0ffcb19 ("ir3: Rewrite register allocation") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27497> (cherry picked from commit aeed5fd98d47be122260bf0c232c2d8dfcd8d400)
2024-02-14anv,driconf: Add sampler coordinate precision workaround for AoE 4Sviatoslav Peleshko
AoE4 samples texture on the edge between texels, which can cause unexpected texel to be returned, and cause misrenderings. This workaround enables coordinate rounding even in NEAREST mode, which fixes the problem. Cc: mesa-stable Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9864 Signed-off-by: Sviatoslav Peleshko <sviatoslav.peleshko@globallogic.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27337> (cherry picked from commit 0a44f6319ef49fd279156cbf37a3144f906bbc3e)
2024-02-14zink: Only call reapply_color_write if EXT_color_write_enable is availableCorentin Noël
Allows to use zink with drivers that do not expose this extension. Backport-to: 23.3 24.0 Reviewed-By: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Signed-off-by: Corentin Noël <corentin.noel@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27516> (cherry picked from commit 72886cbefaa40f5d61c5deee5e125b353d32852f)
2024-02-14.pick_status.json: Update to 90eae30bcb84d54dc871ddbb8355f729cf8fa900Eric Engestrom
2024-02-07meson: upgrade zlib wrap to 1.3.1David Heidelberg
`$ meson wrap update zlib` Cc: mesa-stable Reviewed-by: Dylan Baker <dylan@pnwbakers.com> Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Signed-off-by: David Heidelberg <david.heidelberg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27311> (cherry picked from commit 56f31d1847ba04c8214c68581a3a3c292fd300f4)
2024-02-07frontends/va: Fix updating AV1 rate control parametersDavid Rosca
Follow the same logic as H264. Fixes: 5edbecb8569 ("frontends/va: adding va av1 encoding functions") Reviewed-by: Ruijing Dong <ruijing.dong@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27481> (cherry picked from commit fa8e0ba3f739cb46cf7bb709903c0206f240c584)
2024-02-07aco: fix >8 byte linear vgpr copiesRhys Perry
No fossil-db changes. Signed-off-by: Rhys Perry <pendingchaos02@gmail.com> Reviewed-by: Daniel Schürmann <daniel@schuermann.dev> Cc: mesa-stable Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27436> (cherry picked from commit 174e37afb9ebcd556bc18555ca2aa3276b3d8e04)
2024-02-07anv: flush tile cache independent of format with HIZ-CCS flushTapani Pälli
Cc: mesa-stable Fixes: ba87656079a ("anv: implement undocumented tile cache flush requirements") Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10420 Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10530 Signed-off-by: Tapani Pälli <tapani.palli@intel.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Tested-by: Mark Janes <markjanes@swizzler.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27440> (cherry picked from commit 5178ad761c9e8e86ffb3bc59322ec998c0ae2063)
2024-02-07panfrost: Fix dual-source blendingChristian Duerr
If dual blending is enabled, only 1 output is supported. Multiple outputs confuse the write combining pass in this case, leading to incorrect output and/or an assert failure in emit_fragment_store. The fix is straightforward, just skip the speculative emitting of multiple outputs in the case where dual source blending is enabled. This also adds an extra sanity check in `pan_nir_lower_zs_store` to check for only one blend store being present. Fixes: c65a9be421c ("panfrost: Preprocess shaders at CSO create time") Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9487 Co-Authored-By: Eric R. Smith <eric.smith@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26474> (cherry picked from commit 49c1b404e5e1cf7010855c1345d01c53e3e17ea5)
2024-02-06radv: don't submit 0 length on UVD either.Dave Airlie
The kernel checks for UVD msgs and if there aren't any gets upset, so don't submit 0 length on UVD rings either to avoid that. Cc: mesa-stable Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27186> (cherry picked from commit 47c725b53e41d0f6be81d88051f008447afc4df5)
2024-02-06radv/uvd: uvd kernel checks for full dpb allocation.Dave Airlie
The CTS image allocation sometimes doesn't try to allocate a complete DPB, but the amdgpu kernel module checks for this, so always make the DPB max sized on uvd instances. Fixes part of video decode on Fiji/Polaris Cc: mesa-stable Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27186> (cherry picked from commit df9bc11589bb855629243248b167af663e18a4c0)
2024-02-06radv: init decoder ip block earlier.Dave Airlie
This makes the queue decisions later correct. Cc: mesa-stable Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27186> (cherry picked from commit bba36df84d44a1c2eb8f482ce06642f1ca1c0c19)
2024-02-06radv: fix correct padding on uvdDave Airlie
Fixes: 8a29291dbe6c ("radv/video: add h264 support for uvd") Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27186> (cherry picked from commit 6065671a7fbd1924a11db6cf1af075ad9e487305)
2024-02-06.pick_status.json: Update to fa8e0ba3f739cb46cf7bb709903c0206f240c584Eric Engestrom
2024-02-02venus: refactor query feedback cmdsJuston Li
The list free_query_feedback_cmds for recycling query feedback cmds was only used in vn_command_pool when it was a vn_feedback_cmd_pool. For clarity, refactor and store this list in vn_feedback_cmd_pool instead and introduce a new struct vn_query_feedback_cmd that references the feedback cmd and the feedback cmd pool for tracking. Refactor out the allocation portion of query feedback cmds into its own function for allocating the new vn_query_feedback_cmd struct. Fixes: 5b24ab91e43 ("venus: switch to unconditionally deferred query feedback") Signed-off-by: Juston Li <justonli@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27163> (cherry picked from commit c3417c5bb815722bdedf6ca83ce1466bec14a3f2)
2024-02-02.pick_status.json: Mark 38e92556a041cc421dadb95aaac43a4619311a87 as denominatedEric Engestrom
2024-02-02.pick_status.json: Mark 46f5a226d6613e0a4c7b3a3496e745090fc14429 as denominatedEric Engestrom
2024-02-02zink: run sparse lowering after all optimization passesMike Blumenkrantz
some passes (e.g., opt_shrink_vector) operate on the assumption that sparse tex ops have a certain number of components and then remove components and unset the sparse flag if they can optimize out the sparse usage zink's sparse ops do not have the standard number of components, which causes such passes to make incorrect assumptions and tag them as not being sparse, which breaks everything fix #10540 Fixes: 0d652c0c8db ("zink: shrink vectors during optimization") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27414> (cherry picked from commit 2085d6043804c316939ac47d6b334007872655b7)
2024-02-02zink: move sparse lowering up in fileMike Blumenkrantz
no functional changes Fixes: 0d652c0c8db ("zink: shrink vectors during optimization") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27414> (cherry picked from commit 6a8cd7a64fbf8a91d99a4c3f08a13b53ce5c72d6)
2024-02-02zink: zero allocate resident_defs array in ntvMike Blumenkrantz
this makes assert(def!=0) more reliable Fixes: 73ef54e3424 ("zink: handle residency return value from sparse texture instructions") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27414> (cherry picked from commit aacc4e1c687b643929d496cec72891b814fc2256)
2024-02-02zink: fix sparse bo placementMike Blumenkrantz
the util function here takes a bitmask of memory type indices, not properties. rename the function and correct the usage fixes sparse on nvidia blob Fixes: c71287e70c2 ("zink: correct sparse bo mem_type_idx placement") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27414> (cherry picked from commit 3b025d6b42476d27f5e8d6e2347f85874a50eb72)
2024-02-02.pick_status.json: Mark 7b7a581a52db21ed8826d6f2986ea6dfc208fb2a as denominatedEric Engestrom
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-12 00:37:19 +0000