Hi
- Original Message -
> Hi,
>
> > The benchmarks are quite encouraging, since I get from +-25% for
> > xonotic up to +-100% for glmark. (fwiw, vhost-user-gpu had similar
> > results too). Finally, I tried to make it acceptable for upstream.
>
> Hmm, I don't feel like adding too many mo
Hi,
> The benchmarks are quite encouraging, since I get from +-25% for
> xonotic up to +-100% for glmark. (fwiw, vhost-user-gpu had similar
> results too). Finally, I tried to make it acceptable for upstream.
Hmm, I don't feel like adding too many modes to virgl ...
With vhost-user-gpu giving
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH 00/18] virgl: use a seperate rendering thread
Type: series
Message-id: 20160904222039.11460-1
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 00/18] virgl: use a seperate rendering thread
Type: series
Message-id: 20160904222039.11460-1-marcandre.lur...@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE
Hi,
A while ago, Dave Airlie started implementing a seperate thread for
virgl (although it didn't work for me and was very much in wip
state). I fixed the code so I could test it, and moved it to use qemu
iothread/aio loops, inspired by the dataplane code in the virtio block
devices.
The benchmar
