All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v6 5/8] drm/vmwgfx: Implement an infrastructure for write-coherent resources
Date: Tue, 15 Oct 2019 00:19:53 +0800	[thread overview]
Message-ID: <201910150024.pYGTE8Rq%lkp@intel.com> (raw)
In-Reply-To: <20191014132204.7721-6-thomas_os@shipmail.org>

[-- Attachment #1: Type: text/plain, Size: 3600 bytes --]

Hi "Thomas,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc3 next-20191014]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Thomas-Hellstr-m-VMware/Emulated-coherent-graphics-memory-take-2/20191014-213955
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c: In function 'vmw_mmap':
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c:36:11: error: 'ttm_bo_vm_open' undeclared (first use in this function); did you mean 'ttm_bo_mem_put'?
      .open = ttm_bo_vm_open,
              ^~~~~~~~~~~~~~
              ttm_bo_mem_put
   drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c:36:11: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c:37:12: error: 'ttm_bo_vm_close' undeclared (first use in this function); did you mean 'ttm_bo_vm_open'?
      .close = ttm_bo_vm_close
               ^~~~~~~~~~~~~~~
               ttm_bo_vm_open
--
   drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c: In function 'vmw_bo_vm_mkwrite':
>> drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c:364:8: error: implicit declaration of function 'ttm_bo_vm_reserve'; did you mean 'ttm_bo_unreserve'? [-Werror=implicit-function-declaration]
     ret = ttm_bo_vm_reserve(bo, vmf);
           ^~~~~~~~~~~~~~~~~
           ttm_bo_unreserve
   drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c: In function 'vmw_bo_vm_fault':
>> drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c:414:3: error: 'TTM_BO_VM_NUM_PREFAULT' undeclared (first use in this function)
      TTM_BO_VM_NUM_PREFAULT;
      ^~~~~~~~~~~~~~~~~~~~~~
   drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c:414:3: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c:415:8: error: implicit declaration of function 'ttm_bo_vm_fault_reserved'; did you mean 'ttm_bo_init_reserved'? [-Werror=implicit-function-declaration]
     ret = ttm_bo_vm_fault_reserved(vmf, prot, num_prefault);
           ^~~~~~~~~~~~~~~~~~~~~~~~
           ttm_bo_init_reserved
   cc1: some warnings being treated as errors

vim +36 drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c

    29	
    30	int vmw_mmap(struct file *filp, struct vm_area_struct *vma)
    31	{
    32		static const struct vm_operations_struct vmw_vm_ops = {
    33			.pfn_mkwrite = vmw_bo_vm_mkwrite,
    34			.page_mkwrite = vmw_bo_vm_mkwrite,
    35			.fault = vmw_bo_vm_fault,
  > 36			.open = ttm_bo_vm_open,
  > 37			.close = ttm_bo_vm_close
    38		};
    39		struct drm_file *file_priv = filp->private_data;
    40		struct vmw_private *dev_priv = vmw_priv(file_priv->minor->dev);
    41		int ret = ttm_bo_mmap(filp, vma, &dev_priv->bdev);
    42	
    43		if (ret)
    44			return ret;
    45	
    46		vma->vm_ops = &vmw_vm_ops;
    47	
    48		return 0;
    49	}
    50	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 43784 bytes --]

  reply	other threads:[~2019-10-14 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 13:21 [PATCH v6 0/8] Emulated coherent graphics memory take 2 Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 1/8] mm: Remove BUG_ON mmap_sem not held from xxx_trans_huge_lock() Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 2/8] mm: pagewalk: Take the pagetable lock in walk_pte_range() Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 3/8] mm: Add a walk_page_mapping() function to the pagewalk code Thomas Hellström (VMware)
2019-11-06  3:49   ` Andrew Morton
2019-10-14 13:22 ` [PATCH v6 4/8] mm: Add write-protect and clean utilities for address space ranges Thomas Hellström (VMware)
2019-11-06  3:51   ` Andrew Morton
2019-10-14 13:22 ` [PATCH v6 5/8] drm/vmwgfx: Implement an infrastructure for write-coherent resources Thomas Hellström (VMware)
2019-10-14 16:19   ` kbuild test robot [this message]
2019-10-14 13:22 ` [PATCH v6 6/8] drm/vmwgfx: Use an RBtree instead of linked list for MOB resources Thomas Hellström (VMware)
2019-10-14 13:22 ` [PATCH v6 7/8] drm/vmwgfx: Implement an infrastructure for read-coherent resources Thomas Hellström (VMware)
2019-10-14 13:22 ` [PATCH v6 8/8] drm/vmwgfx: Add surface dirty-tracking callbacks Thomas Hellström (VMware)
2019-10-21 12:24 ` [PATCH v6 0/8] Emulated coherent graphics memory take 2 Thomas Hellstrom
2019-11-04  9:21 ` -mm maintainer? WAS " Thomas Hellström (VMware)
2019-11-04 16:36   ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201910150024.pYGTE8Rq%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.