search for: drm_vm_close

Displaying 5 results from an estimated 5 matches for "drm_vm_close".

Did you mean: drm_gem_close
2007 Sep 03
4
Fixes and workarounds for regressions and issues in the randr-1.2 branch
Hi, Please find attached the patches which I currently use on my desktop machine for dual head with the randr branch to fix the issues which I found. They may help others as well but may e.g. also disable the Xv blitter which might be working for some (but didn't on my card) - more information is found in the text comments in the patches. I have to hurry so this is short, will be back.
2007 Aug 06
3
[Bug 11868] New: Starting X for the second time fails (without reloading drm modules)
..._open_locked] 0x2adf4bae7000,0x00008000 Aug 6 21:11:46 localhost [drm:drm_vm_open_locked] 0x2adf4baef000,0x00010000 Aug 6 21:11:46 localhost [drm:drm_vm_open_locked] 0x2adf4baff000,0x00001000 Aug 6 21:11:46 localhost [drm:drm_vm_shm_close] 0x2adf46288000,0x00002000 Aug 6 21:11:46 localhost [drm:drm_vm_close] 0x2adf47713000,0x04000000 Aug 6 21:11:46 localhost [drm:drm_vm_close] 0x2adf4b713000,0x003c0000 Aug 6 21:11:46 localhost [drm:drm_vm_close] 0x2adf4bad3000,0x00010000 Aug 6 21:11:46 localhost [drm:drm_vm_close] 0x2adf4bae3000,0x00004000 Aug 6 21:11:46 localhost [drm:drm_vm_close] 0x2adf4bae7000...
2015 Sep 09
2
[PATCH 1/5] virtio-gpu: add virtio_gpu_queue_ctrl_buffer_nolock
Add virtio_gpu_queue_ctrl_buffer_nolock function, which does the same as virtio_gpu_queue_ctrl_buffer but does not take the virtqueue lock. The caller must hold the lock instead. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_vq.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git
2015 Sep 10
0
[PATCH 1/5] virtio-gpu: add virtio_gpu_queue_ctrl_buffer_nolock
...ock. The > > caller must hold the lock instead. > > > The drm subsystem tends to use *_locked and *_unlocked suffixes. With > the latter being less common. > Not a big deal but perhaps you can use one of those for virtio ? _locked looks correct for this case to me (looking at drm_vm_close + drm_vm_close_locked to compare). I'll change it. cheers, Gerd
2015 Sep 09
2
[PATCH 1/5] virtio-gpu: add virtio_gpu_queue_ctrl_buffer_nolock
Add virtio_gpu_queue_ctrl_buffer_nolock function, which does the same as virtio_gpu_queue_ctrl_buffer but does not take the virtqueue lock. The caller must hold the lock instead. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_vq.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git