On Mon, Oct 30, 2017 at 10:22:40PM +0800, Matthew J. Francis wrote:
> On 30/10/2017 17:28, Frediano Ziglio wrote:
> > This patch changes ABI so would need a version bump and a Qemu patch.
> > Did you send a patch to Qemu too?
>
> As mentioned in the patch overview, I haven't touched qemu yet - if
On Fri, Nov 03, 2017 at 02:47:17PM +0800, Matthew J. Francis wrote:
> Following up to myself:
> I got at least two things wrong in the above analysis.
>
> Firstly, in the Xspice case, we control both ends of the fake uinput
> connection (written to by vdagentd, read from by the "xspice pointer"
>
>
> Jonathon Jongsma writes:
>
> > I sent two of these patches earlier (one ACKed by Frediano), but decided
> > to do a little more cleanup here. There are a couple of basic issues
> > related to the Stream stuff:
> > 1. The word Stream is used in a couple of ways within the spice-server
> >
Reduce the needs to buffer the entire frame and than send
and on the other end to wait the entire frame before processing.
Some encodings allow to start processing before having a full
frame allowing to reduce latency and buffering with huge frames.
Signed-off-by: Frediano Ziglio
---
common/mess
This flag will allow the client to perform some optimisations
on output and buffering processing.
Old clients will ignore this additional flag.
Signed-off-by: Frediano Ziglio
---
spice.proto | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/spice.proto b/spice.proto
index 867
Reduce the needs to buffer the entire frame and than send
and on the other end to wait the entire frame before processing.
Some encodings allow to start processing before having a full
frame allowing to reduce latency and buffering with huge frames.
Signed-off-by: Frediano Ziglio
---
spice/proto
> I followed the section " GL acceleration (virgl) " of spice-user-manual.html
> to configure my host , but it always failed ,
> i updated my environment like this : qemu 2.10 , libvirt 3.6 , spice-server
> 0.13.90 , spice-gtk 0.33, spice-protocol 0.12.12 , virglrenderer 0.6.0 , but
> it still did
