| 9fb01062 | 09-Apr-2026 |
Maarten Lankhorst <dev@lankhorst.se> |
drm/ttm/tests: Remove checks from ttm_pool_free_no_dma_alloc
On !x86, the pool type is never initialised, and the pages are freed back to the system.
The test broke on the list_lru rewrite, but I'm
drm/ttm/tests: Remove checks from ttm_pool_free_no_dma_alloc
On !x86, the pool type is never initialised, and the pages are freed back to the system.
The test broke on the list_lru rewrite, but I'm not sure how that it was supposed to work previously. In the meantime CI is broken so reverting for now.
Fixes: 444e2a19d7fd ("ttm/pool: port to list_lru. (v2)") Cc: Christian Koenig <christian.koenig@amd.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Dave Chinner <david@fromorbit.com> Cc: Christian König <christian.koenig@amd.com> Cc: Dave Airlie <airlied@redhat.com> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se> Signed-off-by: Dave Airlie <airlied@redhat.com> Link: https://patch.msgid.link/20260409142658.1511941-2-dev@lankhorst.se
show more ...
|
| 3b053cd7 | 09-Apr-2026 |
Matthew Auld <matthew.auld@intel.com> |
drm/ttm/tests: fix lru_count ASSERT
On pool init we should expect the lru_count for each node to be zeroed as per __list_lru_init -> init_one_lru, but here we are asserting the opposite.
Currently
drm/ttm/tests: fix lru_count ASSERT
On pool init we should expect the lru_count for each node to be zeroed as per __list_lru_init -> init_one_lru, but here we are asserting the opposite.
Currently our CI is blowing up with:
10:23:33] # ttm_device_init_pools: ASSERTION FAILED at drivers/gpu/drm/ttm/tests/ttm_device_test.c:178 [10:23:33] Expected !list_lru_count(&pt.pages) to be false, but is true [10:23:33] [FAILED] DMA allocations, DMA32 required [10:23:33] [PASSED] No DMA allocations, DMA32 required [10:23:33] # ttm_device_init_pools: ASSERTION FAILED at drivers/gpu/drm/ttm/tests/ttm_device_test.c:178 [10:23:33] Expected !list_lru_count(&pt.pages) to be false, but is true
Fixes: 444e2a19d7fd ("ttm/pool: port to list_lru. (v2)") Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Matthew Brost <matthew.brost@intel.com> Cc: Christian Koenig <christian.koenig@amd.com> Cc: Dave Airlie <airlied@redhat.com> Reviewed-by: Ryszard Knop <ryszard.knop@intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com> Link: https://patch.msgid.link/20260409121512.81298-3-matthew.auld@intel.com
show more ...
|
| d11ac904 | 09-Mar-2026 |
Thadeu Lima de Souza Cascardo <cascardo@igalia.com> |
drm/ttm/tests: add a test to exercise ttm_bo_swapout
Currently, ttm_bo_swapout is not exercised by the TTM KUnit tests.
It used to be exercised until commit 76689eb52667 ("drm/ttm: remove ttm_bo_va
drm/ttm/tests: add a test to exercise ttm_bo_swapout
Currently, ttm_bo_swapout is not exercised by the TTM KUnit tests.
It used to be exercised until commit 76689eb52667 ("drm/ttm: remove ttm_bo_validate_swapout test"), but that test was removed as it was unreliable due to requiring to allocate half of the system memory.
Calling ttm_bo_swapout directly with a single allocated BO, however, does not suffer from that problem, and was able to detect a UAF introduced by commit c06da4b3573a ("drm/ttm: Tidy usage of local variables a little bit"), when built with KASAN.
When applying a fix to that UAF, the test passed without any issues.
Cc: Tvrtko Ursulin <tvrtko.ursulin@igalia.com> Cc: Christian König <christian.koenig@amd.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@igalia.com> Signed-off-by: Tvrtko Ursulin <tursulin@ursulin.net> Link: https://lore.kernel.org/r/20260309-ttm_bo_swapout_test-v2-1-219f64046cfe@igalia.com
show more ...
/linux/Documentation/devicetree/bindings/arm/qcom.yaml/linux/Documentation/devicetree/bindings/display/panel/abt,y030xx067a.yaml/linux/Documentation/devicetree/bindings/display/panel/advantech,idk-1110wr.yaml/linux/Documentation/devicetree/bindings/display/panel/advantech,idk-2121wr.yaml/linux/Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.yaml/linux/Documentation/devicetree/bindings/display/panel/dlc,dlc0700yzg-1.yaml/linux/Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml/linux/Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml/linux/Documentation/devicetree/bindings/display/panel/ilitek,ili9163.yaml/linux/Documentation/devicetree/bindings/display/panel/ilitek,ili9322.yaml/linux/Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml/linux/Documentation/devicetree/bindings/display/panel/innolux,ej030na.yaml/linux/Documentation/devicetree/bindings/display/panel/innolux,p097pfg.yaml/linux/Documentation/devicetree/bindings/display/panel/jadard,jd9365da-h3.yaml/linux/Documentation/devicetree/bindings/display/panel/kingdisplay,kd035g6-54nt.yaml/linux/Documentation/devicetree/bindings/display/panel/lgphilips,lb035q02.yaml/linux/Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml/linux/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml/linux/Documentation/devicetree/bindings/display/panel/mitsubishi,aa121td01.yaml/linux/Documentation/devicetree/bindings/display/panel/motorola,mot-panel.yaml/linux/Documentation/devicetree/bindings/display/panel/nec,nl8048hl11.yaml/linux/Documentation/devicetree/bindings/display/panel/novatek,nt36523.yaml/linux/Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml/linux/Documentation/devicetree/bindings/display/panel/orisetech,otm8009a.yaml/linux/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml/linux/Documentation/devicetree/bindings/display/panel/panel-simple.yaml/linux/Documentation/devicetree/bindings/display/panel/pda,91-00156-a0.yaml/linux/Documentation/devicetree/bindings/display/panel/raydium,rm68200.yaml/linux/Documentation/devicetree/bindings/display/panel/raydium,rm692e5.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,ld9040.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,lms380kf01.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,lms397kf04.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,s6d27a1.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,s6d7aa0.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,s6e3ha8.yaml/linux/Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.yaml/linux/Documentation/devicetree/bindings/display/panel/sgd,gktw70sdae4se.yaml/linux/Documentation/devicetree/bindings/display/panel/sitronix,st7701.yaml/linux/Documentation/devicetree/bindings/display/panel/sitronix,st7789v.yaml/linux/Documentation/devicetree/bindings/display/panel/sony,acx565akm.yaml/linux/Documentation/devicetree/bindings/display/panel/startek,kd070fhfid015.yaml/linux/Documentation/devicetree/bindings/display/panel/tpo,td.yaml/linux/Documentation/devicetree/bindings/display/panel/visionox,r66451.yaml/linux/Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml/linux/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml/linux/Documentation/devicetree/bindings/vendor-prefixes.yaml/linux/MAINTAINERS/linux/drivers/accel/amdxdna/aie2_pci.c/linux/drivers/accel/amdxdna/aie2_pci.h/linux/drivers/accel/amdxdna/amdxdna_pci_drv.c/linux/drivers/accel/ivpu/ivpu_gem.c/linux/drivers/accel/ivpu/ivpu_hw_40xx_reg.h/linux/drivers/accel/ivpu/ivpu_hw_ip.c/linux/drivers/dma-buf/heaps/cma_heap.c/linux/drivers/gpu/buddy.c/linux/drivers/gpu/drm/bridge/analogix/Kconfig/linux/drivers/gpu/drm/bridge/analogix/anx7625.c/linux/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c/linux/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.h/linux/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-hdcp.c/linux/drivers/gpu/drm/drm_gem_shmem_helper.c/linux/drivers/gpu/drm/imagination/pvr_gem.c/linux/drivers/gpu/drm/loongson/lsdc_drv.c/linux/drivers/gpu/drm/loongson/lsdc_gem.c/linux/drivers/gpu/drm/loongson/lsdc_gem.h/linux/drivers/gpu/drm/mxsfb/lcdif_drv.c/linux/drivers/gpu/drm/panel/Kconfig/linux/drivers/gpu/drm/panel/Makefile/linux/drivers/gpu/drm/panel/panel-ilitek-ili9882t.c/linux/drivers/gpu/drm/panel/panel-jadard-jd9365da-h3.c/linux/drivers/gpu/drm/panel/panel-lxd-m9189a.c/linux/drivers/gpu/drm/panel/panel-mantix-mlaf057we51.c/linux/drivers/gpu/drm/panel/panel-motorola-mot.c/linux/drivers/gpu/drm/panel/panel-novatek-nt37700f.c/linux/drivers/gpu/drm/panel/panel-renesas-r61307.c/linux/drivers/gpu/drm/panel/panel-renesas-r69328.c/linux/drivers/gpu/drm/panel/panel-simple.c/linux/drivers/gpu/drm/panthor/panthor_sched.cttm_bo_validate_test.c/linux/drivers/gpu/drm/ttm/ttm_bo.c/linux/drivers/gpu/drm/vc4/vc4_hdmi.c/linux/drivers/gpu/tests/gpu_buddy_test.c/linux/include/linux/gpu_buddy.h/linux/include/uapi/drm/amdxdna_accel.h |
| 76689eb5 | 10-Jul-2025 |
Christian König <christian.koenig@amd.com> |
drm/ttm: remove ttm_bo_validate_swapout test
The test is quite fragile since it tries to allocate halve available system memory + 1 page.
If the system has either not enough memory to make the allo
drm/ttm: remove ttm_bo_validate_swapout test
The test is quite fragile since it tries to allocate halve available system memory + 1 page.
If the system has either not enough memory to make the allocation work with other things running in parallel or to much memory so the allocation fails as to large/invalid the test will fail.
Completely remove the test. We already validate swapout on the device level and that test seems to be stable.
Signed-off-by: Christian König <christian.koenig@amd.com> Reviewed-by: Matthew Brost <matthew.brost@intel.com> Link: https://lore.kernel.org/r/20250710144129.1803-2-christian.koenig@amd.com
show more ...
|