diff options
| author |   Zack Rusin <zackr@vmware.com> | 2021-07-23 12:51:51 -0400 |
|---|---|---|
| committer | Zack Rusin <zackr@vmware.com> | 2021-07-28 14:53:23 -0400 |
| commit | 2b273544f5800a38673883fc591ce4d83a2bedb3 (patch) | |
| tree | 5734dc7f26f699198bc30f01a94f310a72b92063 /drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | |
| parent | drm/vmwgfx: Switch to using DRM_IOCTL_DEF_DRV (diff) | |
| download | linux-dev-2b273544f5800a38673883fc591ce4d83a2bedb3.tar.xz linux-dev-2b273544f5800a38673883fc591ce4d83a2bedb3.zip | |
drm/vmwgfx: Cleanup logging
The code was using the old DRM logging functions, which made it
hard to figure out what was coming from vmwgfx. The newer logging
helpers include the driver name in the logs and make it explicit
which driver they're coming from. This allows us to standardize
our logging a bit and clean it up in the process.
vmwgfx is a little special because technically the hardware it's
running on can be anything from the last 12 years or so which is
why we need to include capabilities in the logs in the first
place or otherwise we'd have no way of knowing what were
the capabilities of the platform the guest was running in.
Signed-off-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210723165153.113198-2-zackr@vmware.com
Diffstat (limited to 'drivers/gpu/drm/vmwgfx/vmwgfx_drv.h')
| -rw-r--r-- | drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h index 356f82c26f59..375b01cccd1a 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h @@ -367,7 +367,8 @@ enum vmw_display_unit_type { vmw_du_invalid = 0, vmw_du_legacy, vmw_du_screen_object, - vmw_du_screen_target + vmw_du_screen_target, + vmw_du_max }; struct vmw_validation_context; |