[PATCH 1/2] drm: qxl: Remove dead qxl_io_flush_* functions

2025-04-13 Thread linux
From: "Dr. David Alan Gilbert" qxl_io_flush_release() and qxl_io_flush_surfaces() were both added in 2013's commit f64122c1f6ad ("drm: add new QXL driver. (v1.4)") but have remained unused. Remove them. Signed-off-by: Dr. David Alan Gilbert --- drivers/gpu/drm/qxl/qxl_cmd.c | 10 --

[PATCH 0/2] drm: qxl: Deadcoding

2025-04-13 Thread linux
From: "Dr. David Alan Gilbert" Hi, A couple of small deadcodings for qxl. The first just cleans up a couple of trivial unusued wrappers. The second cleans out some debugfs code that's been unused for a few years. Dave Signed-off-by: Dr. David Alan Gilbert Dr. David Alan Gilbert (2): drm:

[PATCH 2/2] drm: qxl: Remove unused debugfs code

2025-04-13 Thread linux
From: "Dr. David Alan Gilbert" qxl_debugfs_add_files() has been unused since 2022's commit d0719e09264b ("drm/qxl: Use TTM builtin resource manager debugfs code") Remove it. This now leaves the debugfs_count and debugfs members of struct qxl_device unused. Remove them. QXL_DEBUGFS_MAX_COMPONE

Re: [Spice-devel] Bug#1054514: linux-image-6.1.0-13-amd64: Debian VM with qxl graphics freezes frequently

2023-12-06 Thread Linux regression tracking (Thorsten Leemhuis)
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting for once, to make this easily accessible to everyone. Gerd, it seems this regression[1] fell through the cracks. Could you please take a look? Or is there a good reason why this can't be addressed? Or was it dealt

Re: [PATCH 1/1] drm/qxl: fixes qxl_fence_wait

2024-03-25 Thread Linux regression tracking (Thorsten Leemhuis)
x27;s why I'm asking. Would be really good to finally get this resolved... Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did s

Re: [Regression] 6.9.0: WARNING: workqueue: WQ_MEM_RECLAIM ttm:ttm_bo_delayed_delete [ttm] is flushing !WQ_MEM_RECLAIM events:qxl_gc_work [qxl]

2024-05-09 Thread Linux regression tracking (Thorsten Leemhuis)
On 08.05.24 14:35, Anders Blomdell wrote: > On 2024-05-07 07:04, Linux regression tracking (Thorsten Leemhuis) wrote: >> On 06.05.24 16:30, David Wang wrote: >>>> On 30.04.24 08:13, David Wang wrote: >> >>>> And confirmed that the warning is caused by >&g

Re: [Regression] 6.9.0: WARNING: workqueue: WQ_MEM_RECLAIM ttm:ttm_bo_delayed_delete [ttm] is flushing !WQ_MEM_RECLAIM events:qxl_gc_work [qxl]

2024-05-09 Thread Linux regression tracking (Thorsten Leemhuis)
On 06.05.24 16:30, David Wang wrote: >> On 30.04.24 08:13, David Wang wrote: >> And confirmed that the warning is caused by >> 07ed11afb68d94eadd4ffc082b97c2331307c5ea and reverting it can fix. > > The kernel warning still shows up in 6.9.0-rc7. > (I think 4 high load processes on a 2-Core VM c

Re: [REGRESSION] QXL display malfunction

2024-06-13 Thread Linux regression tracking (Thorsten Leemhuis)
[CCing a few more people and lists that get_maintainers pointed out for qxl] Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting for once, to make this easily accessible to everyone. Thomas, from here it looks like this report that apparently is caused by a change of yours

Re: [REGRESSION] QXL display malfunction

2024-07-02 Thread Linux regression tracking (Thorsten Leemhuis)
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting for once, to make this easily accessible to everyone. Thomas, was there some progress wrt to fixing below regression? I might have missed something, but from here it looks like this fall through the cracks. Makes me wond