Displaying 20 results from an estimated 10000 matches similar to: "[PATCH v5 0/4] virgl: fence fd support"
2018 Nov 05
2
[PATCH v4 3/4] drm/virtio: add in/out fence support for explicit synchronization
On Mon, 5 Nov 2018 at 11:42, Robert Foss <robert.foss at collabora.com> wrote:
>
> When the execbuf call receives an in-fence it will get the dma_fence
> related to that fence fd and wait on it before submitting the draw call.
>
> On the out-fence side we get fence returned by the submitted draw call
> and attach it to a sync_file and send the sync_file fd to userspace. On
2018 Nov 05
2
[PATCH v4 3/4] drm/virtio: add in/out fence support for explicit synchronization
On Mon, 5 Nov 2018 at 11:42, Robert Foss <robert.foss at collabora.com> wrote:
>
> When the execbuf call receives an in-fence it will get the dma_fence
> related to that fence fd and wait on it before submitting the draw call.
>
> On the out-fence side we get fence returned by the submitted draw call
> and attach it to a sync_file and send the sync_file fd to userspace. On
2018 Nov 12
0
[PATCH v4 3/4] drm/virtio: add in/out fence support for explicit synchronization
On Fri, Nov 09, 2018 at 06:13:52PM +0100, Robert Foss wrote:
> Hey Gerd,
>
> On 2018-11-09 11:13, Gerd Hoffmann wrote:
> > On Mon, Nov 05, 2018 at 05:25:05PM +0000, Emil Velikov wrote:
> > > On Mon, 5 Nov 2018 at 11:42, Robert Foss <robert.foss at collabora.com> wrote:
> > > >
> > > > When the execbuf call receives an in-fence it will get the
2014 Jul 22
0
[PATCH 09/17] drm/radeon: use common fence implementation for fences
On Tue, Jul 22, 2014 at 5:59 PM, Christian K?nig
<deathsimple at vodafone.de> wrote:
> Am 22.07.2014 17:42, schrieb Daniel Vetter:
>
>> On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig
>> <christian.koenig at amd.com> wrote:
>>>
>>> Drivers exporting fences need to provide a fence->signaled and a
>>> fence->wait
>>> function,
2014 Jul 22
1
[PATCH 09/17] drm/radeon: use common fence implementation for fences
> Maybe I've mixed things up a bit in my description. There is
> fence_signal which the implementor/exporter of a fence must call when
> the fence is completed. If the exporter has an ->enable_signaling
> callback it can delay that call to fence_signal for as long as it
> wishes as long as enable_signaling isn't called yet. But that's just
> the optimization to not
2018 Nov 02
0
[PATCH 2/5] drm/virtio: add uapi for in and out explicit fences
On Thu, 1 Nov 2018 at 12:56, Robert Foss <robert.foss at collabora.com> wrote:
> On 2018-10-31 10:38, Emil Velikov wrote:
> > Hi Rob,
> >
> > On Thu, 25 Oct 2018 at 19:38, Robert Foss <robert.foss at collabora.com> wrote:
> >>
> >> Add a new field called fence_fd that will be used by userspace to send
> >> in-fences to the kernel and
2020 Apr 07
0
[vhost:vhost 32/44] drivers/gpu/drm/virtio/virtgpu_ioctl.c:113:7: error: implicit declaration of function 'copy_from_user'; did you mean 'sg_copy_from_buffer'?
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
head: 4e6ebec0de18aaea5f5f814b25bfcae3751c6369
commit: 013a472de94693ba05696d59e7df3224c20a22e6 [32/44] virtio: stop using legacy struct vring in kernel
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce:
wget
2019 Jun 28
1
[PATCH v5 09/12] drm/virtio: rework virtio_gpu_object_create fencing
Use gem reservation helpers and direct reservation_object_* calls
instead of ttm.
v5: fix fencing (Chia-I Wu).
v3: Due to using the gem reservation object it is initialized and ready
for use before calling ttm_bo_init, so we can also drop the tricky fence
logic which checks whenever the command is in flight still. We can
simply fence our object before submitting the virtio command and be done
2016 Sep 02
0
[ANNOUNCE] intel-gpu-tools 1.16
Hello,
A new intel-gpu-tools quarterly release is available with the following
changes:
- Build automatically tests required when issueing a make check, Tests/subtests
that receive a crash signal should print a backtrace when i-g-t is built with
libunwind support (Marius Vlad)
- lib/igt_kms: Force connector probing on first use (Chris Wilson)
- vc4: Add a test for BO lookup failure error path
2018 Jan 11
3
[PATCH 0/3] drm/nouveau: Add support for fence FDs
From: Thierry Reding <treding at nvidia.com>
This small series of patches implements support for waiting on and
emitting fence FDs on kickoff. This enables explicit fencing and can be
used for example to synchronize buffer accesses between the display
engine and the GPU on Tegra.
The first patch lays the groundwork by splitting up nouveau_fence_sync()
to allow reuse. Patch 2 is where the
2015 Oct 02
0
[PATCH v3 4/7] virtio-gpu: add 3d/virgl support
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie <airlied at redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
drivers/gpu/drm/virtio/Makefile | 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 15 +
drivers/gpu/drm/virtio/virtgpu_drv.h | 60 ++++
2015 Oct 02
0
[PATCH v3 4/7] virtio-gpu: add 3d/virgl support
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie <airlied at redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
drivers/gpu/drm/virtio/Makefile | 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 15 +
drivers/gpu/drm/virtio/virtgpu_drv.h | 60 ++++
2015 Sep 21
0
[PATCH v2 4/6] virtio-gpu: add 3d/virgl support
On Mon, Sep 21, 2015 at 11:40:15AM +0200, Gerd Hoffmann wrote:
> Add the bits needed for opengl rendering support: query
> capabilities, new virtio commands, drm ioctls.
>
> Signed-off-by: Dave Airlie <airlied at redhat.com>
> Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
Looks good to me overall.
Some minor comments below.
I had to fix dri-devel mailing list
2019 May 03
2
[PATCH] drm/virtio: Remove redundant return type
virtio_gpu_fence_emit() always returns 0, since it
has no error paths.
Consequently no calls for virtio_gpu_fence_emit()
use the return value, and it can be removed.
Signed-off-by: Robert Foss <robert.foss at collabora.com>
Suggested-by: Emil Velikov <emil.velikov at collabora.com>
---
This patch was suggested in this email thread:
[PATCH] drm/virtio: allocate fences with
2015 Sep 09
3
[PATCH 3/5] update virtio gpu driver: add 3d/virgl support
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie <airlied at redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
drivers/gpu/drm/virtio/Makefile | 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 10 +
drivers/gpu/drm/virtio/virtgpu_drv.h | 60 ++++
2015 Sep 09
3
[PATCH 3/5] update virtio gpu driver: add 3d/virgl support
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie <airlied at redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
drivers/gpu/drm/virtio/Makefile | 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 10 +
drivers/gpu/drm/virtio/virtgpu_drv.h | 60 ++++
2019 May 06
1
[PATCH v2] drm/virtio: Remove redundant return type
virtio_gpu_fence_emit() always returns 0, since it
has no error paths.
Consequently no calls for virtio_gpu_fence_emit()
use the return value, and it can be removed.
Signed-off-by: Robert Foss <robert.foss at collabora.com>
Suggested-by: Emil Velikov <emil.velikov at collabora.com>
Reviewed-by: Chia-I Wu <olvaffe at gmail.com>
---
This patch was suggested in this email thread:
2017 Jun 09
1
[ANNOUNCE] intel-gpu-tools 1.19
A new intel-gpu-tools quarterly release is available with the
following changes:
Library changes:
- Changed debugfs handlers to open files for the DRM device in use,
for setups with more than one DRM device. (Tomeu Vizoso)
- Added support for 4K and audio HDMI EDID injection. (Abdiel
Janulgue, Marius Vlad)
- Added support for AMDGPU devices. (Chris Wilson)
Tools changes:
-
2016 Dec 02
1
[ANNOUNCE] intel-gpu-tools 1.17
A new intel-gpu-tools quarterly release is available with the
following changes:
Library changes:
- Added an iterator that generate primes for creating input data that
should not fall into any patterns that may be optimised by the
drivers. (Chris Wilson)
- Crashes in fixture blocks now print a stacktrace. (Marius Vlad)
- Added support for various system suspend/resume options. (Imre Deak)
2016 May 31
0
[ANNOUNCE] intel-gpu-tools 1.15
Hello,
A new intel-gpu-tools quarterly release is available with the following
changes:
- New KMS test: tests/kms_cursor_legacy (Stress legacy cursor ioctl)
(Chris Wilson)
- Several GEM tests have been removed from BAT: tests/gem_exec_whisper,
tests/gem_sync (dropped individual engines), test/gem_cs_prefetch (replaced
by test/gem_exec_gttfill), tests/gem_ctx_param_basic (got relabeled
to