kernel/drivers/gpu/drm/vmwgfx/vmwgfx_marker.c, branch linux-4.17.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y2014-07-23T22:01:50Zdrm: vmwgfx: Use nsec based interfaces2014-07-23T22:01:50ZThomas Gleixnertglx@linutronix.de2014-07-16T21:05:07Zurn:sha1:f166e6dcb7225c4193bcda68c9346583ed78b186
No point in converting timespecs back and forth.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Thomas Hellstrom <thellstrom@vmware.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
vmwgfx: Fix confusion caused by using "fence" in various places2011-09-06T10:48:40ZThomas Hellstromthellstrom@vmware.com2011-09-01T20:18:42Zurn:sha1:6bcd8d3c782b7b2c98c8f414a6bb43cf6b84e53c
This is needed before we introduce the fence objects.
Otherwise this will be even more confusing. The plan is to use the following:
seqno: A 32-bit sequence number that may be passed in the fifo.
marker: Objects, carrying a seqno, that track fifo submission time. They
are used for fifo lag based throttling.
fence objects: Kernel space objects, possibly accessible from user-space and
carrying a 32-bit seqno together with signaled status.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Jakob Bornecrantz <jakob@vmware.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>