Core Tests

Core Tests — Tests for core drm ioctls and behaviour

Programs

Description

core_auth

Call drmGetMagic() and drmAuthMagic() and see if it behaves.

getclient-simple

Check drm client is always authenticated.

getclient-master-drop

Use 2 clients, check second is authenticated even when first dropped.

basic-auth

Test magic numbers for master and slave.

many-magics

Test authentication and magic numbers uniqness for rlimit slaves.


core_getclient

Tests the DRM_IOCTL_GET_CLIENT ioctl.


core_getstats

Tests the DRM_IOCTL_GET_STATS ioctl.


core_getversion

Tests the DRM_IOCTL_GET_VERSION ioctl and libdrm's drmGetVersion() interface to it.

basic

Check GET_VERSION ioctl of the first drm device.

all-cards

Check GET_VERSION ioctl for all drm devices.


core_hotunplug

Examine behavior of a driver on device hot unplug

unbind-rebind

Check if the driver can be cleanly unbound from a device believed to be closed, then rebound

unplug-rescan

Check if a device believed to be closed can be cleanly unplugged, then restored

hotunbind-rebind

Check if the driver can be cleanly unbound from an open device, then released and rebound

hotunplug-rescan

Check if an open device can be cleanly unplugged, then released and restored

hotrebind

Check if the driver can be cleanly rebound to a device with a still open hot unbound driver instance

hotreplug

Check if a hot unplugged and still open device can be cleanly restored

hotrebind-lateclose

Check if a hot unbound driver instance still open after hot rebind can be cleanly released

hotreplug-lateclose

Check if an instance of a still open while hot replugged device can be cleanly released


core_setmaster

Check that Drop/SetMaster behaves correctly wrt root/user access

master-drop-set-root

Ensure that root can Set/DropMaster

master-drop-set-user

Ensure first normal user can Set/DropMaster

master-drop-set-shared-fd

Check the Set/DropMaster behaviour on shared fd


core_setmaster_vs_auth

Check that drop/setMaster correctly transfer master state