drm/vmwgfx: Use a validation context allocator for relocations and validations

Browse source

A common trait of these objects are that they are allocated during the
command validation phase and freed after command submission. Furthermore
they are accessed by a single thread only. So provide a simple unprotected
stack-like allocator from which these objects can be allocated. Their
memory is freed with the validation context when the command submission
is done.

Note that the mm subsystem maintains a per-cpu cache of single pages to
make single page allocation and freeing efficient.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>

...

This commit is contained in:

Thomas Hellstrom 2018-09-26 15:36:52 +02:00

parent 2724b2d54c

commit fc18afcf5f

4 changed files with 132 additions and 64 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

12

drivers/gpu/drm/vmwgfx/vmwgfx_drv.h

View file

80

drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c

View file

92

drivers/gpu/drm/vmwgfx/vmwgfx_validation.c

View file

12

drivers/gpu/drm/vmwgfx/vmwgfx_validation.h

View file