> > > + typedef struct VhostUserGpuMsg {
> > > + uint32_t request; /* VhostUserGpuRequest */
> > > + uint32_t flags;
> > > + uint32_t size; /* the following payload size */
> >
> > uint32_t padding;
> >
> > > + union {
> > > + VhostUserGpuCursorPos cursor_pos;
> > > +
Hi
On Tue, May 14, 2019 at 7:38 AM Gerd Hoffmann wrote:
>
> Hi,
>
> > +VhostUserGpuCursorUpdate
> > +
> > +
> > ++-+---+---++
> > +| pos | hot_x | hot_y | cursor |
> > ++-+---+---++
> > +
> > +:pos: a ``VhostUserGpuCursorPos``,
Hi,
> +VhostUserGpuCursorUpdate
> +
> +
> ++-+---+---++
> +| pos | hot_x | hot_y | cursor |
> ++-+---+---++
> +
> +:pos: a ``VhostUserGpuCursorPos``, the cursor location
> +
> +:hot_x/hot_y: ``u32``, the cursor hot location
> +
>
Add a new vhost-user message to give a unix socket to a vhost-user
backend for GPU display updates.
Back when I started that work, I added a new GPU channel because the
vhost-user protocol wasn't bidirectional. Since then, there is a
vhost-user-slave channel for the slave to send requests to the
