All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/7] drm/ttm: Handle cgroup based eviction in TTM
Date: Fri, 25 Oct 2024 12:12:11 +0800	[thread overview]
Message-ID: <202410251208.99Kwkppv-lkp@intel.com> (raw)
In-Reply-To: <20241023075302.27194-4-maarten.lankhorst@linux.intel.com>

Hi Maarten,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next next-20241024]
[cannot apply to tj-cgroup/for-next drm-xe/drm-xe-next akpm-mm/mm-everything drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.12-rc4]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Maarten-Lankhorst/kernel-cgroup-Add-dev-memory-accounting-cgroup/20241023-155504
base:   git://anongit.freedesktop.org/drm/drm drm-next
patch link:    https://lore.kernel.org/r/20241023075302.27194-4-maarten.lankhorst%40linux.intel.com
patch subject: [PATCH 3/7] drm/ttm: Handle cgroup based eviction in TTM
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20241025/202410251208.99Kwkppv-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241025/202410251208.99Kwkppv-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410251208.99Kwkppv-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/ttm/ttm_bo.c:1100: warning: Function parameter or struct member 'hit_low' not described in 'ttm_bo_swapout_walk'
>> drivers/gpu/drm/ttm/ttm_bo.c:1100: warning: Function parameter or struct member 'evict_low' not described in 'ttm_bo_swapout_walk'


vim +1100 drivers/gpu/drm/ttm/ttm_bo.c

a3185f91d0579b Christian König   2022-05-09  1089  
10efe34dae798c Thomas Hellström  2024-07-05  1090  /**
10efe34dae798c Thomas Hellström  2024-07-05  1091   * struct ttm_bo_swapout_walk - Parameters for the swapout walk
10efe34dae798c Thomas Hellström  2024-07-05  1092   */
10efe34dae798c Thomas Hellström  2024-07-05  1093  struct ttm_bo_swapout_walk {
10efe34dae798c Thomas Hellström  2024-07-05  1094  	/** @walk: The walk base parameters. */
10efe34dae798c Thomas Hellström  2024-07-05  1095  	struct ttm_lru_walk walk;
10efe34dae798c Thomas Hellström  2024-07-05  1096  	/** @gfp_flags: The gfp flags to use for ttm_tt_swapout() */
10efe34dae798c Thomas Hellström  2024-07-05  1097  	gfp_t gfp_flags;
e5a692062aad1c Maarten Lankhorst 2024-10-23  1098  
e5a692062aad1c Maarten Lankhorst 2024-10-23  1099  	bool hit_low, evict_low;
10efe34dae798c Thomas Hellström  2024-07-05 @1100  };
10efe34dae798c Thomas Hellström  2024-07-05  1101  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-10-25  4:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  7:52 [PATCH 0/7] kernel/cgroups: Add "dev" memory accounting cgroup Maarten Lankhorst
2024-10-23  7:52 ` [PATCH 1/7] kernel/cgroup: " Maarten Lankhorst
2024-10-23 15:26   ` Waiman Long
2024-11-11  9:28     ` Maarten Lankhorst
2024-10-25  5:44   ` kernel test robot
2024-10-28 14:53   ` Friedrich Vock
2024-11-11 22:53     ` Maarten Lankhorst
2024-11-14  8:45       ` Friedrich Vock
2024-10-23  7:52 ` [PATCH 2/7] drm/drv: Add drmm cgroup registration for dev cgroups Maarten Lankhorst
2024-10-23  8:45   ` Jani Nikula
2024-10-24 10:35   ` kernel test robot
2024-10-24 15:42   ` kernel test robot
2024-10-23  7:52 ` [PATCH 3/7] drm/ttm: Handle cgroup based eviction in TTM Maarten Lankhorst
2024-10-24 11:37   ` kernel test robot
2024-10-24 17:37   ` kernel test robot
2024-10-25  4:12   ` kernel test robot [this message]
2024-10-23  7:52 ` [PATCH 4/7] drm/xe: Implement cgroup for vram Maarten Lankhorst
2024-10-23  7:52 ` [PATCH 5/7] drm/amdgpu: Add cgroups implementation Maarten Lankhorst
2024-10-23  7:52 ` [PATCH 6/7] [HACK] drm/xe: Hack to test with mapped pages instead of vram Maarten Lankhorst
2024-10-23  8:52   ` Jani Nikula
2024-10-23  7:53 ` [PATCH 7/7] [DISCUSSION] drm/gem: Add cgroup memory accounting Maarten Lankhorst
2024-10-24 14:07   ` kernel test robot
2024-10-23  8:11 ` ✓ CI.Patch_applied: success for kernel/cgroups: Add "dev" memory accounting cgroup Patchwork
2024-10-23  8:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-23  8:12 ` ✗ CI.KUnit: failure " Patchwork
2024-10-23 19:40 ` [PATCH 0/7] " Tejun Heo
2024-10-24  7:20   ` Maxime Ripard
2024-10-24 17:06     ` Tejun Heo
2024-10-28 10:05       ` Maxime Ripard
2024-10-29 20:38         ` Johannes Weiner
2024-11-06 10:31           ` Maxime Ripard
2024-11-06 18:20             ` Tejun Heo
2024-11-13 14:58               ` Maarten Lankhorst
2024-11-13 18:29                 ` Tejun Heo

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=202410251208.99Kwkppv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.