Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1685771 > unrolled thread
| Started by | Kirti Wankhede <kwankhede@nvidia.com> |
|---|---|
| First post | 2017-07-12 15:20 +0200 |
| Last post | 2017-07-14 12:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations Kirti Wankhede <kwankhede@nvidia.com> - 2017-07-12 15:20 +0200
Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations Gerd Hoffmann <kraxel@redhat.com> - 2017-07-14 12:00 +0200
| From | Kirti Wankhede <kwankhede@nvidia.com> |
|---|---|
| Date | 2017-07-12 15:20 +0200 |
| Subject | Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations |
| Message-ID | <u2pIC-g1-15@gated-at.bofh.it> |
Hey Gerd, Sorry, I missed this mail earlier. On 6/21/2017 12:52 PM, Gerd Hoffmann wrote: > 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? > If cursor surface is not provided, a dot for cursor is seen on the primary surface, which is pretty much usable. >> 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? > We need to create a GRAPHIC_CONSOLE for vGPU device and specify GraphicHwOps so that from its .gfx_update callback, surface can be queried and updated. >> 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? > What is default refresh rate of QEMU if vnc is connected? Thanks, Kirti > 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 >
[toc] | [next] | [standalone]
| From | Gerd Hoffmann <kraxel@redhat.com> |
|---|---|
| Date | 2017-07-14 12:00 +0200 |
| Message-ID | <u35ya-1D9-13@gated-at.bofh.it> |
| In reply to | #1685771 |
Hi, > > > 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? > > > > We need to create a GRAPHIC_CONSOLE for vGPU device and specify > GraphicHwOps so that from its .gfx_update callback, surface can be > queried and updated. Yes, you need GraphicHwOps, but there is no need to have a VGACommonState for that. > > > 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? > > > > What is default refresh rate of QEMU if vnc is connected? /* in ms */ #define GUI_REFRESH_INTERVAL_DEFAULT 30 #define GUI_REFRESH_INTERVAL_IDLE 3000 cheers, Gerd
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web