All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 04/11] drm/vmwgfx: stop using ttm_bo_create
Date: Wed, 23 Sep 2020 11:50:05 +0800	[thread overview]
Message-ID: <202009231114.qqmpPHsJ%lkp@intel.com> (raw)
In-Reply-To: <20200921144856.2797-5-christian.koenig@amd.com>

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

Hi "Christian,

I love your patch! Perhaps something to improve:

[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on next-20200922]
[cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next tegra-drm/drm/tegra/for-next linus/master drm/drm-next v5.9-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-ttm-add-ttm_bo_pin-ttm_bo_unpin/20200921-234857
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-randconfig-a005-20200921 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 4e8c028158b56d9c2142a62464e8e0686bde3584)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

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

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/vmwgfx/vmwgfx_bo.c:518:8: warning: expression which evaluates to zero treated as a null pointer constant of type 'struct ttm_operation_ctx *' [-Wnon-literal-null-conversion]
                                      false, acc_size, NULL, NULL, NULL);
                                      ^~~~~
   1 warning generated.

# https://github.com/0day-ci/linux/commit/4f52191faabdaf44db9409b13ccea5ec0da52704
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Christian-K-nig/drm-ttm-add-ttm_bo_pin-ttm_bo_unpin/20200921-234857
git checkout 4f52191faabdaf44db9409b13ccea5ec0da52704
vim +518 drivers/gpu/drm/vmwgfx/vmwgfx_bo.c

   489	
   490	/**
   491	 * vmw_bo_create_kernel - Create a pinned BO for internal kernel use.
   492	 *
   493	 * @dev_priv: Pointer to the device private struct
   494	 * @size: size of the BO we need
   495	 * @placement: where to put it
   496	 * @p_bo: resulting BO
   497	 *
   498	 * Creates and pin a simple BO for in kernel use.
   499	 */
   500	int vmw_bo_create_kernel(struct vmw_private *dev_priv, unsigned long size,
   501				 struct ttm_placement *placement,
   502				 struct ttm_buffer_object **p_bo)
   503	{
   504		unsigned npages = PAGE_ALIGN(size) >> PAGE_SHIFT;
   505		struct ttm_buffer_object *bo;
   506		size_t acc_size;
   507		int ret;
   508	
   509		bo = kzalloc(sizeof(*bo), GFP_KERNEL);
   510		if (unlikely(!bo))
   511			return -ENOMEM;
   512	
   513		acc_size = ttm_round_pot(sizeof(*bo));
   514		acc_size += ttm_round_pot(npages * sizeof(void *));
   515		acc_size += ttm_round_pot(sizeof(struct ttm_tt));
   516		ret = ttm_bo_init_reserved(&dev_priv->bdev, bo, size,
   517					   ttm_bo_type_device, placement, 0,
 > 518					   false, acc_size, NULL, NULL, NULL);
   519		if (unlikely(ret))
   520			goto error_free;
   521	
   522		ttm_bo_pin(bo);
   523		ttm_bo_unreserve(bo);
   524		*p_bo = bo;
   525	
   526		return 0;
   527	
   528	error_free:
   529		kfree(bo);
   530		return ret;
   531	}
   532	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

  parent reply	other threads:[~2020-09-23  3:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 14:48 Nuke TTM_PL_FLAG_NO_EVICT Christian König
2020-09-21 14:48 ` [PATCH 01/11] drm/ttm: add ttm_bo_pin()/ttm_bo_unpin() Christian König
2020-09-21 14:48 ` [PATCH 02/11] drm/radeon: switch over to the new pin interface Christian König
2020-09-21 14:48 ` [PATCH 03/11] drm/vmwgfx: remove unused placement combination Christian König
2020-09-21 14:48 ` [PATCH 04/11] drm/vmwgfx: stop using ttm_bo_create Christian König
2020-09-22  6:45   ` Thomas Zimmermann
2020-09-22  8:25     ` Christian König
2020-09-23  3:50   ` kernel test robot [this message]
2020-09-23 16:40   ` kernel test robot
2020-09-21 14:48 ` [PATCH 05/11] drm/vmwgfx: switch over to the new pin interface Christian König
2020-09-21 14:48 ` [PATCH 06/11] drm/vram-helper: " Christian König
2020-09-22  6:44   ` Thomas Zimmermann
2020-09-21 14:48 ` [PATCH 07/11] drm/qxl: " Christian König
2020-09-22  6:20   ` Gerd Hoffmann
2020-09-21 14:48 ` [PATCH 08/11] drm/nouveau: " Christian König
2020-09-21 14:48 ` [PATCH 09/11] drm/amdgpu: " Christian König
2020-09-21 14:48 ` [PATCH 10/11] drm/ttm: remove ttm_bo_create Christian König
2020-09-21 14:48 ` [PATCH 11/11] drm/ttm: remove TTM_PL_FLAG_NO_EVICT Christian König

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=202009231114.qqmpPHsJ%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.