Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display device driver interface

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Oleksandr Grytsov writes ("Re: [Xen-devel] [PATCH v1 0/2] libxl: add PV display 
device driver interface"):
> After internal discussion we think that putting positions and
> z-orders of virtual connectors to the Xen store and libxl
> configuration is not so good idea. Because their composition depends
> on an application and usage. We consider automotive usage.  For
> example one of domain drives navigation system and depends on
> scenario the navigation window position and size can be changed. In
> that case on the host should be an instance of window manager or
> something like that.  The window manager will decide where to put
> the virtual displays.

Right.

> If it is ok, following is libxl/xl configuration proposal:

This looks much better to me.  (See of course Wei's point about the
connector list ambiguity.)

Can you sketch out what the rest of the system does, then ?
Presumably there has to be a different control protocol to your
backend, to tell it where to put the actual displays.  I think it
would be good if that protocol were the same for different use cases,
and documented somewhere.

So for example, when a window manager moves a window, how is the
backend told where to display the guest output ?

Your final patches should come with changese to the xl.cfg
documentation, but I think we can still discuss this in generalities
for now and then the text you write in your emails or example comments
will make a good starting point for the xl.cfg documentation.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel