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

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

 



  Hi,

> "we only support" seems to just state the use cases before adding
> vGPU but we are trying to support vGPU cases.
> If even we decide that for vGPU cards we always have monitor_id == 0

Yes, we want this for sure.  One channel per display.

> (that is multiple DisplayChannels for each vGPU) we still have the
> issue of id matching with the agent which these patches are trying to
> deal with.

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.

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]