Re: [PATCH] drm/virtio: allocate fences with GFP_KERNEL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03.05.19 16:31, Emil Velikov wrote:
On Mon, 29 Apr 2019 at 23:10, Chia-I Wu <olvaffe@xxxxxxxxx> wrote:

It was changed to GFP_ATOMIC in commit ec2f0577c (add & use
virtio_gpu_queue_fenced_ctrl_buffer) because the allocation happened
with a spinlock held.  That was no longer true after commit
9fdd90c0f (add virtio_gpu_alloc_fence()).

Signed-off-by: Chia-I Wu <olvaffe@xxxxxxxxx>
Cc: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Cc: Gustavo Padovan <gustavo.padovan@xxxxxxxxxxxxx>
Cc: Robert Foss <robert.foss@xxxxxxxxxxxxx>

Reviewed-by: Emil Velikov <emil.velikov@xxxxxxxxxxxxx>

Side:
Rob, should we follow-up on 9fdd90c0f and drop the
virtio_gpu_fence_emit() return type?

Good idea. None of the called functions return anything.
I'll get right on it.


Rob.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel




[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux