Re: [RFC PATCH v2 00/20] Monitor ID rework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2018-08-24 at 17:21 +0200, Gerd Hoffmann wrote:
> On Fri, Aug 24, 2018 at 03:38:07PM +0200, Lukáš Hrázký wrote:
> > At this moment, the agent has no idea about channel_ids,
> 
> I think this one should be solved.
> 
> So, qemu knows which channel id belongs to which device (and head, in
> case devices have one channel per head like virtio).  qemu could pass
> that information to spice-server, so vdagent can query it
> from spice-server.
> 
> Then vdagent can scan /dev/dri/card*, query the outputs of each device
> (using libdrm), lookup the device in sysfs, build a channel-id -> output
> mapping from that.

Ok, supposing this is the first issue we should look into, could you
describe the process in more detail? What values are used, passed over
interfaces and translating into what, etc...

In particular how do you map the devices in sysfs exactly to (e.g.
xrandr) outputs?

Thanks!
Lukas
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux Virtualization]     [Linux Virtualization]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]