ClientNativePixmapFactoryDmabuf uses ioctl, instead of drmIoctl.

ui/gfx/linux/client_native_pixmap_dmabuf.cc

Index: ui/gfx/linux/client_native_pixmap_dmabuf.cc
diff --git a/ui/gfx/linux/client_native_pixmap_dmabuf.cc b/ui/gfx/linux/client_native_pixmap_dmabuf.cc
index d656c338f0a6d9eb86e9a3e0a1dd304559d4e28e..c655fb8c5f3ec557bdb2976898bc128228908977 100644
--- a/ui/gfx/linux/client_native_pixmap_dmabuf.cc
+++ b/ui/gfx/linux/client_native_pixmap_dmabuf.cc
@@ -7,6 +7,7 @@
 #include <fcntl.h>
 #include <linux/version.h>
 #include <stddef.h>
+#include <sys/ioctl.h>
 #include <sys/mman.h>
 #include <xf86drm.h>
 
@@ -17,26 +18,23 @@
 #include "base/strings/stringprintf.h"
 #include "base/trace_event/trace_event.h"
 
-#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 6, 0)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 6, 0)

[dshwang, 2017/04/06 00:56:31]

I want to change it to
#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 6, 0) || defined(OS_CHROMEOS)

However, it makes build fail for current_os="chromeos" in Ubuntu.

+#include <linux/dma-buf.h>
+#else
 #include <linux/types.h>
 
-struct local_dma_buf_sync {
+struct dma_buf_sync {
   __u64 flags;
 };
 
-#define LOCAL_DMA_BUF_SYNC_READ (1 << 0)
-#define LOCAL_DMA_BUF_SYNC_WRITE (2 << 0)
-#define LOCAL_DMA_BUF_SYNC_RW \
-  (LOCAL_DMA_BUF_SYNC_READ | LOCAL_DMA_BUF_SYNC_WRITE)
-#define LOCAL_DMA_BUF_SYNC_START (0 << 2)
-#define LOCAL_DMA_BUF_SYNC_END (1 << 2)
-
-#define LOCAL_DMA_BUF_BASE 'b'
-#define LOCAL_DMA_BUF_IOCTL_SYNC \
-  _IOW(LOCAL_DMA_BUF_BASE, 0, struct local_dma_buf_sync)
+#define DMA_BUF_SYNC_READ (1 << 0)
+#define DMA_BUF_SYNC_WRITE (2 << 0)
+#define DMA_BUF_SYNC_RW (DMA_BUF_SYNC_READ | DMA_BUF_SYNC_WRITE)
+#define DMA_BUF_SYNC_START (0 << 2)
+#define DMA_BUF_SYNC_END (1 << 2)
 
-#else
-#include <linux/dma-buf.h>
+#define DMA_BUF_BASE 'b'
+#define DMA_BUF_IOCTL_SYNC _IOW(DMA_BUF_BASE, 0, struct dma_buf_sync)
 #endif
 
 namespace gfx {
@@ -44,24 +42,24 @@ namespace gfx {
 namespace {
 
 void PrimeSyncStart(int dmabuf_fd) {
-  struct local_dma_buf_sync sync_start = {0};
+  struct dma_buf_sync sync_start = {0};
 
-  sync_start.flags = LOCAL_DMA_BUF_SYNC_START | LOCAL_DMA_BUF_SYNC_RW;
+  sync_start.flags = DMA_BUF_SYNC_START | DMA_BUF_SYNC_RW;
 #if DCHECK_IS_ON()
   int rv =
 #endif
-      drmIoctl(dmabuf_fd, LOCAL_DMA_BUF_IOCTL_SYNC, &sync_start);
+      ioctl(dmabuf_fd, DMA_BUF_IOCTL_SYNC, &sync_start);

[marcheu, 2017/04/06 00:56:11]

ioctl returns an error value, you have to check it and react accordingly

[dshwang, 2017/04/06 01:19:24]

new patch set wraps it by HANDLE_EINTR like other ioctl code in chromium.
if it return error from HANDLE_EINTR, I don't have idea how we should handle it.
It means kernel has some bug about it, and user may see some artifacts as sync
failed.

   DPLOG_IF(ERROR, rv) << "Failed DMA_BUF_SYNC_START";
 }
 
 void PrimeSyncEnd(int dmabuf_fd) {
-  struct local_dma_buf_sync sync_end = {0};
+  struct dma_buf_sync sync_end = {0};
 
-  sync_end.flags = LOCAL_DMA_BUF_SYNC_END | LOCAL_DMA_BUF_SYNC_RW;
+  sync_end.flags = DMA_BUF_SYNC_END | DMA_BUF_SYNC_RW;
 #if DCHECK_IS_ON()
   int rv =
 #endif
-      drmIoctl(dmabuf_fd, LOCAL_DMA_BUF_IOCTL_SYNC, &sync_end);
+      ioctl(dmabuf_fd, DMA_BUF_IOCTL_SYNC, &sync_end);
   DPLOG_IF(ERROR, rv) << "Failed DMA_BUF_SYNC_END";
 }