[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1498029758.5802.1.camel@redhat.com>
Date: Wed, 21 Jun 2017 09:22:38 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Kirti Wankhede <kwankhede@...dia.com>,
Alex Williamson <alex.williamson@...hat.com>
Cc: Xiaoguang Chen <xiaoguang.chen@...el.com>,
chris@...is-wilson.co.uk, intel-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, zhenyuw@...ux.intel.com,
zhiyuan.lv@...el.com, intel-gvt-dev@...ts.freedesktop.org,
zhi.a.wang@...el.com, kevin.tian@...el.com
Subject: Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations
Hi,
> We don't support cursor for console vnc. Ideally console vnc should
> be
> used by admin for configuration or during maintenance, which refresh
> primary surface at low refresh rate, 10 fps.
But you surely want a mouse pointer for the admin?
You render it directly to the primary surface then I guess?
> Right we need to know this at device initialization time for both
> cases
> to initialize VGACommonState structure for that device
Why do you need a VGACommonState?
> and also need
> NONE to decide whether to init console vnc or not. We have a
> mechanism
> to disable console vnc path and we recommend to disable it for better
> performance.
Hmm, maybe we should have a ioctl to configure the refresh rate, or a
ioctl to allow qemu ask for a refresh when needed?
qemu can throttle the display update rate, which for example happens in
case no vnc client is connected. qemu updates the display only once
every few seconds then.
cheers,
Gerd
Powered by blists - more mailing lists