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

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

 



  Hi,

> > Yes, we want this for sure.  One channel per display.
> 
> Maybe you cut too much context. Who is "we" in the above sentence?
> Why "we want"?

See other reply.

> > Yes.  *That* is the underlying problem.  There is no guest-visible link
> > between display device and spice channel.  Except when the device is
> > qxl, because qxl has a channel-id field somewhere (in qxl rom IIRC)
> > which the guest can read.
> > 
> > And it is not limited to vGPU.  Try place two emulated display devices
> > into one guest (not using qxl).  You'll face the very same issue.
> > 
> > Placing both channel_id and monitor_id into the messages isn't going to
> > solve this.
> 
> Yes, we have 2 issues:
> a) display_id = channel_id ? channel_id : monitor_id formula (that can
>    be solved with channel_id and monitor_id instead of using display_id);

I'm not sure we have to solve this one.  What is the use case?  If you
use qxl as boot display in a vgpu setup, would you seriously want
multiple monitors on the qxl device?

> b) vdagent not knowing what a given display_id is.

Yes.  And I think this should be tackled for classic display channels
too, not only streaming channels.

cheers,
  Gerd

_______________________________________________
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]