drm/vmwgfx: Switch the internal BO's to ttm_bo_type_kernel

There's never a need to access our internal kernel bo's from
user-space. Those objects are used exclusively for internal
support to guest backed surfaces (in otable setup and mob
page tables) and there's no need to have them be of device
type, i.e. mmappable from user-space.

Signed-off-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20211105193845.258816-6-zackr@vmware.com

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c
index fd007f1c177635a1d225a8896ae4b19de0d3edf5..c97a3d5e90ced01b45da27cec6c16a46ff1861e5 100644 (file)
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c
@@ -494,7 +494,7 @@ int vmw_bo_create_kernel(struct vmw_private *dev_priv, unsigned long size,
        drm_vma_node_reset(&bo->base.vma_node);
 
        ret = ttm_bo_init_reserved(&dev_priv->bdev, bo, size,
-                                  ttm_bo_type_device, placement, 0,
+                                  ttm_bo_type_kernel, placement, 0,
                                   &ctx, NULL, NULL, NULL);
        if (unlikely(ret))
                goto error_account;