···297297 * @version: Allows expanding the execbuf ioctl parameters without breaking298298 * backwards compatibility, since user-space will always tell the kernel299299 * which version it uses.300300- * @flags: Execbuf flags. None currently.300300+ * @flags: Execbuf flags.301301+ * @imported_fence_fd: FD for a fence imported from another device301302 *302303 * Argument to the DRM_VMW_EXECBUF Ioctl.303304 */304305305306#define DRM_VMW_EXECBUF_VERSION 2307307+308308+#define DRM_VMW_EXECBUF_FLAG_IMPORT_FENCE_FD (1 << 0)309309+#define DRM_VMW_EXECBUF_FLAG_EXPORT_FENCE_FD (1 << 1)306310307311struct drm_vmw_execbuf_arg {308312 __u64 commands;···316312 __u32 version;317313 __u32 flags;318314 __u32 context_handle;319319- __u32 pad64;315315+ __s32 imported_fence_fd;320316};321317322318/**···332328 * @passed_seqno: The highest seqno number processed by the hardware333329 * so far. This can be used to mark user-space fence objects as signaled, and334330 * to determine whether a fence seqno might be stale.331331+ * @fd: FD associated with the fence, -1 if not exported335332 * @error: This member should've been set to -EFAULT on submission.336333 * The following actions should be take on completion:337334 * error == -EFAULT: Fence communication failed. The host is synchronized.···350345 __u32 mask;351346 __u32 seqno;352347 __u32 passed_seqno;353353- __u32 pad64;348348+ __s32 fd;354349 __s32 error;355350};356351