1. 03 1月, 2017 2 次提交
  2. 20 12月, 2016 2 次提交
    • G
      virtio-gpu: track and limit host memory allocations · 9b7621bc
      Gerd Hoffmann 提交于
      This patch makes virtio-gpu track host memory allocations for ressources
      and applies a limit (configurable 256M by default).  When exceeding the
      limit virtio-gpu throws VIRTIO_GPU_RESP_ERR_OUT_OF_MEMORY errors (like
      it already does today when pixman image allocations fail).
      
      This patch covers 2d mode only.  For 3d mode we have to figure how we
      are going to handle this best.  qemu doesn't track resources in case
      virglrenderer is used, so I guess we should extend virglrenderer to
      allow setting a limit, then let qemu set the limit and catch
      virgl_renderer_resource_create failures.
      
      Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
      Cc: Dave Airlie <airlied@redhat.com>
      Cc: 李强 <liqiang6-s@360.cn>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Message-id: 1480423356-22255-1-git-send-email-kraxel@redhat.com
      9b7621bc
    • P
      display: virtio-gpu-3d: check virgl capabilities max_size · abd7f08b
      Prasad J Pandit 提交于
      Virtio GPU device while processing 'VIRTIO_GPU_CMD_GET_CAPSET'
      command, retrieves the maximum capabilities size to fill in the
      response object. It continues to fill in capabilities even if
      retrieved 'max_size' is zero(0), thus resulting in OOB access.
      Add check to avoid it.
      Reported-by: NZhenhao Hong <zhenhaohong@gmail.com>
      Signed-off-by: NPrasad J Pandit <pjp@fedoraproject.org>
      Message-id: 20161214070156.23368-1-ppandit@redhat.com
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      abd7f08b
  3. 15 12月, 2016 4 次提交
  4. 14 12月, 2016 1 次提交
  5. 07 12月, 2016 6 次提交
  6. 06 12月, 2016 20 次提交
  7. 05 12月, 2016 5 次提交