On Wed, Sep 4, 2019 at 12:48 AM Gerd Hoffmann wrote:
>
> Only call virtio_gpu_array_add_fence if we actually have a fence.
>
> Fixes: da758d51968a ("drm/virtio: rework virtio_gpu_execbuffer_ioctl fencing")
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_vq.c | 9 +
>
On Wed, Jul 3, 2019 at 11:31 AM Chia-I Wu wrote:
>
> On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
> >
> > Some helper functions to manage an array of gem objects.
> >
> > v6:
> > - add ticket to struct virtio_gpu_object_array.
> > - add v
.
On Wed, Jun 19, 2019 at 11:08 PM Gerd Hoffmann wrote:
>
> virtio-gpu basically needs a sg_table for the bo, to tell the host where
> the backing pages for the object are. So the gem shmem helpers are a
> perfect fit. Some drm_gem_object_funcs need thin wrappers to update the
> host state, but
On Wed, Jun 19, 2019 at 11:08 PM Gerd Hoffmann wrote:
>
> Some helper functions to manage an array of gem objects.
>
> v4: make them virtio-private instead of generic helpers.
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_drv.h | 10 ++
> drivers/gpu/drm/virtio/virt
struct trace_entry went out-of-sync with the kernel since
commit b000c8065 "tracing: Remove the extra 4 bytes of padding in events"
causing "perf timechart" to be broken.
Signed-off-by: Chia-I Wu
---
tools/perf/builtin-timechart.c | 1 -
1 file changed, 1 deletion(-)
dif
5 matches
Mail list logo