From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 02/10] drm/sched: Move schedule policy to scheduler / entity
Date: Tue, 4 Apr 2023 15:24:16 +0800 [thread overview]
Message-ID: <202304041537.dcZw4xgl-lkp@intel.com> (raw)
In-Reply-To: <20230404002211.3611376-3-matthew.brost@intel.com>
Hi Matthew,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-tip/drm-tip]
[also build test ERROR on linus/master v6.3-rc5 next-20230403]
[cannot apply to drm-misc/drm-misc-next drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes]
[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/Matthew-Brost/drm-sched-Convert-drm-scheduler-to-use-a-work-queue-rather-than-kthread/20230404-082438
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link: https://lore.kernel.org/r/20230404002211.3611376-3-matthew.brost%40intel.com
patch subject: [RFC PATCH 02/10] drm/sched: Move schedule policy to scheduler / entity
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20230404/202304041537.dcZw4xgl-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.1.0
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
# https://github.com/intel-lab-lkp/linux/commit/432d13aa8af1c693fa15eb5a442931332de31937
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Matthew-Brost/drm-sched-Convert-drm-scheduler-to-use-a-work-queue-rather-than-kthread/20230404-082438
git checkout 432d13aa8af1c693fa15eb5a442931332de31937
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/dma-buf/ drivers/gpu/drm/v3d/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304041537.dcZw4xgl-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/v3d/v3d_sched.c: In function 'v3d_sched_init':
>> drivers/gpu/drm/v3d/v3d_sched.c:403:30: error: 'ULL' undeclared (first use in this function)
403 | ULL, "v3d_render", DRM_SCHED_POLICY_DEFAULT,
| ^~~
drivers/gpu/drm/v3d/v3d_sched.c:403:30: note: each undeclared identifier is reported only once for each function it appears in
vim +/ULL +403 drivers/gpu/drm/v3d/v3d_sched.c
381
382 int
383 v3d_sched_init(struct v3d_dev *v3d)
384 {
385 int hw_jobs_limit = 1;
386 int job_hang_limit = 0;
387 int hang_limit_ms = 500;
388 int ret;
389
390 ret = drm_sched_init(&v3d->queue[V3D_BIN].sched,
391 &v3d_bin_sched_ops, NULL,
392 hw_jobs_limit, job_hang_limit,
393 msecs_to_jiffies(hang_limit_ms), NULL,
394 NULL, "v3d_bin", DRM_SCHED_POLICY_DEFAULT,
395 v3d->drm.dev);
396 if (ret)
397 return ret;
398
399 ret = drm_sched_init(&v3d->queue[V3D_RENDER].sched,
400 &v3d_render_sched_ops, NULL,
401 hw_jobs_limit, job_hang_limit,
402 msecs_to_jiffies(hang_limit_ms), NULL,
> 403 ULL, "v3d_render", DRM_SCHED_POLICY_DEFAULT,
404 v3d->drm.dev);
405 if (ret)
406 goto fail;
407
408 ret = drm_sched_init(&v3d->queue[V3D_TFU].sched,
409 &v3d_tfu_sched_ops, NULL,
410 hw_jobs_limit, job_hang_limit,
411 msecs_to_jiffies(hang_limit_ms), NULL,
412 NULL, "v3d_tfu", DRM_SCHED_POLICY_DEFAULT,
413 v3d->drm.dev);
414 if (ret)
415 goto fail;
416
417 if (v3d_has_csd(v3d)) {
418 ret = drm_sched_init(&v3d->queue[V3D_CSD].sched,
419 &v3d_csd_sched_ops, NULL,
420 hw_jobs_limit, job_hang_limit,
421 msecs_to_jiffies(hang_limit_ms), NULL,
422 NULL, "v3d_csd", DRM_SCHED_POLICY_DEFAULT,
423 v3d->drm.dev);
424 if (ret)
425 goto fail;
426
427 ret = drm_sched_init(&v3d->queue[V3D_CACHE_CLEAN].sched,
428 &v3d_cache_clean_sched_ops, NULL,
429 hw_jobs_limit, job_hang_limit,
430 msecs_to_jiffies(hang_limit_ms), NULL,
431 NULL, "v3d_cache_clean",
432 DRM_SCHED_POLICY_DEFAULT, v3d->drm.dev);
433 if (ret)
434 goto fail;
435 }
436
437 return 0;
438
439 fail:
440 v3d_sched_fini(v3d);
441 return ret;
442 }
443
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-04 7:25 UTC|newest]
Thread overview: 176+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 0:22 [Intel-xe] [RFC PATCH 00/10] Xe DRM scheduler and long running workload plans Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 01/10] drm/sched: Convert drm scheduler to use a work queue rather than kthread Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-06-09 6:58 ` [Intel-xe] " Boris Brezillon
2023-06-09 6:58 ` Boris Brezillon
2023-07-31 0:56 ` [Intel-xe] " Matthew Brost
2023-07-31 0:56 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 02/10] drm/sched: Move schedule policy to scheduler / entity Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 7:24 ` kernel test robot [this message]
2023-04-05 17:37 ` [Intel-xe] " Luben Tuikov
2023-04-05 17:37 ` Luben Tuikov
2023-04-05 18:29 ` [Intel-xe] " Matthew Brost
2023-04-05 18:29 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 03/10] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 04/10] drm/sched: Add generic scheduler message interface Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-05-04 5:28 ` [Intel-xe] " Luben Tuikov
2023-05-04 5:28 ` Luben Tuikov
2023-07-31 2:42 ` [Intel-xe] " Matthew Brost
2023-07-31 2:42 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 05/10] drm/sched: Start run wq before TDR in drm_sched_start Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 06/10] drm/sched: Submit job before starting TDR Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-05-04 5:23 ` [Intel-xe] " Luben Tuikov
2023-05-04 5:23 ` Luben Tuikov
2023-07-31 1:00 ` [Intel-xe] " Matthew Brost
2023-07-31 1:00 ` Matthew Brost
2023-07-31 7:26 ` [Intel-xe] " Boris Brezillon
2023-07-31 7:26 ` Boris Brezillon
2023-08-31 19:48 ` [Intel-xe] " Luben Tuikov
2023-08-31 19:48 ` Luben Tuikov
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 07/10] drm/sched: Add helper to set TDR timeout Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-05-04 5:28 ` [Intel-xe] " Luben Tuikov
2023-05-04 5:28 ` Luben Tuikov
2023-07-31 1:09 ` [Intel-xe] " Matthew Brost
2023-07-31 1:09 ` Matthew Brost
2023-08-31 19:52 ` [Intel-xe] " Luben Tuikov
2023-08-31 19:52 ` Luben Tuikov
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 08/10] dma-buf/dma-fence: Introduce long-running completion fences Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 5:18 ` kernel test robot
2023-04-04 9:09 ` [Intel-xe] " Christian König
2023-04-04 9:09 ` Christian König
2023-04-04 12:54 ` [Intel-xe] " Thomas Hellström
2023-04-04 12:54 ` Thomas Hellström
2023-04-04 13:10 ` [Intel-xe] " Christian König
2023-04-04 13:10 ` Christian König
2023-04-04 18:14 ` [Intel-xe] " Thomas Hellström (Intel)
2023-04-04 18:14 ` Thomas Hellström (Intel)
2023-04-04 19:02 ` [Intel-xe] " Matthew Brost
2023-04-04 19:02 ` Matthew Brost
2023-04-04 19:25 ` [Intel-xe] " Daniel Vetter
2023-04-04 19:25 ` Daniel Vetter
2023-04-04 19:48 ` [Intel-xe] " Matthew Brost
2023-04-04 19:48 ` Matthew Brost
2023-04-05 13:09 ` [Intel-xe] " Daniel Vetter
2023-04-05 13:09 ` Daniel Vetter
2023-04-05 23:58 ` [Intel-xe] " Matthew Brost
2023-04-05 23:58 ` Matthew Brost
2023-04-06 6:32 ` [Intel-xe] " Daniel Vetter
2023-04-06 6:32 ` Daniel Vetter
2023-04-06 16:58 ` [Intel-xe] " Matthew Brost
2023-04-06 16:58 ` Matthew Brost
2023-04-06 17:09 ` [Intel-xe] " Daniel Vetter
2023-04-06 17:09 ` Daniel Vetter
2023-04-05 12:35 ` [Intel-xe] " Thomas Hellström
2023-04-05 12:35 ` Thomas Hellström
2023-04-05 12:39 ` [Intel-xe] " Christian König
2023-04-05 12:39 ` Christian König
2023-04-05 12:45 ` [Intel-xe] " Daniel Vetter
2023-04-05 12:45 ` Daniel Vetter
2023-04-05 14:08 ` [Intel-xe] " Christian König
2023-04-05 14:08 ` Christian König
2023-04-04 19:00 ` [Intel-xe] " Daniel Vetter
2023-04-04 19:00 ` Daniel Vetter
2023-04-04 20:03 ` [Intel-xe] " Matthew Brost
2023-04-04 20:03 ` Matthew Brost
2023-04-04 20:11 ` [Intel-xe] " Daniel Vetter
2023-04-04 20:11 ` Daniel Vetter
2023-04-04 20:19 ` [Intel-xe] " Matthew Brost
2023-04-04 20:19 ` Matthew Brost
2023-04-04 20:31 ` [Intel-xe] " Daniel Vetter
2023-04-04 20:31 ` Daniel Vetter
2023-04-04 20:46 ` [Intel-xe] " Matthew Brost
2023-04-04 20:46 ` Matthew Brost
2023-04-04 14:45 ` kernel test robot
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 09/10] drm/sched: Support long-running sched entities Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 0:22 ` [Intel-xe] [RFC PATCH 10/10] drm/syncobj: Warn on long running dma-fences Matthew Brost
2023-04-04 0:22 ` Matthew Brost
2023-04-04 0:24 ` [Intel-xe] ✗ CI.Patch_applied: failure for Xe DRM scheduler and long running workload plans Patchwork
2023-04-04 1:07 ` [Intel-xe] [RFC PATCH 00/10] " Asahi Lina
2023-04-04 1:07 ` Asahi Lina
2023-04-04 1:58 ` [Intel-xe] " Matthew Brost
2023-04-04 1:58 ` Matthew Brost
2023-04-08 7:05 ` [Intel-xe] " Asahi Lina
2023-04-08 7:05 ` Asahi Lina
2023-04-11 14:07 ` [Intel-xe] " Daniel Vetter
2023-04-11 14:07 ` Daniel Vetter
2023-04-12 5:47 ` [Intel-xe] " Asahi Lina
2023-04-12 5:47 ` Asahi Lina
2023-04-12 8:18 ` [Intel-xe] " Daniel Vetter
2023-04-12 8:18 ` Daniel Vetter
2023-04-17 0:03 ` [Intel-xe] " Matthew Brost
2023-04-17 0:03 ` Matthew Brost
2023-04-04 9:04 ` [Intel-xe] " Christian König
2023-04-04 9:04 ` Christian König
2023-04-04 13:23 ` [Intel-xe] " Matthew Brost
2023-04-04 13:23 ` Matthew Brost
2023-04-04 9:13 ` [Intel-xe] " Christian König
2023-04-04 9:13 ` Christian König
2023-04-04 13:37 ` [Intel-xe] " Matthew Brost
2023-04-04 13:37 ` Matthew Brost
2023-04-05 7:41 ` [Intel-xe] " Christian König
2023-04-05 7:41 ` Christian König
2023-04-05 8:34 ` [Intel-xe] " Daniel Vetter
2023-04-05 8:34 ` Daniel Vetter
2023-04-05 8:53 ` [Intel-xe] " Christian König
2023-04-05 8:53 ` Christian König
2023-04-05 9:07 ` [Intel-xe] " Daniel Vetter
2023-04-05 9:07 ` Daniel Vetter
2023-04-05 9:57 ` [Intel-xe] " Christian König
2023-04-05 9:57 ` Christian König
2023-04-05 10:12 ` [Intel-xe] " Daniel Vetter
2023-04-05 10:12 ` Daniel Vetter
2023-04-06 2:08 ` [Intel-xe] " Matthew Brost
2023-04-06 2:08 ` Matthew Brost
2023-04-06 6:37 ` [Intel-xe] " Daniel Vetter
2023-04-06 6:37 ` Daniel Vetter
2023-04-06 10:14 ` [Intel-xe] " Christian König
2023-04-06 10:14 ` Christian König
2023-04-06 10:32 ` [Intel-xe] " Daniel Vetter
2023-04-06 10:32 ` Daniel Vetter
2023-04-04 9:43 ` [Intel-xe] " Tvrtko Ursulin
2023-04-04 9:43 ` Tvrtko Ursulin
2023-04-04 9:48 ` [Intel-xe] " Christian König
2023-04-04 9:48 ` Christian König
2023-04-04 13:43 ` [Intel-xe] " Matthew Brost
2023-04-04 13:43 ` Matthew Brost
2023-04-04 13:52 ` [Intel-xe] " Matthew Brost
2023-04-04 13:52 ` Matthew Brost
2023-04-04 17:29 ` [Intel-xe] " Tvrtko Ursulin
2023-04-04 17:29 ` Tvrtko Ursulin
2023-04-04 19:07 ` [Intel-xe] " Daniel Vetter
2023-04-04 19:07 ` Daniel Vetter
2023-04-04 18:02 ` [Intel-xe] " Zeng, Oak
2023-04-04 18:02 ` Zeng, Oak
2023-04-04 18:08 ` [Intel-xe] " Matthew Brost
2023-04-04 18:08 ` Matthew Brost
2023-04-05 7:30 ` [Intel-xe] " Christian König
2023-04-05 7:30 ` Christian König
2023-04-05 8:42 ` [Intel-xe] " Daniel Vetter
2023-04-05 8:42 ` Daniel Vetter
2023-04-05 18:06 ` [Intel-xe] " Zeng, Oak
2023-04-05 18:06 ` Zeng, Oak
2023-04-05 18:53 ` [Intel-xe] " Matthew Brost
2023-04-05 18:53 ` Matthew Brost
2023-04-06 10:04 ` [Intel-xe] " Christian König
2023-04-06 10:04 ` Christian König
2023-04-07 0:20 ` [Intel-xe] " Zeng, Oak
2023-04-07 0:20 ` Zeng, Oak
2023-04-11 9:02 ` [Intel-xe] " Christian König
2023-04-11 9:02 ` Christian König
2023-04-11 14:13 ` [Intel-xe] " Daniel Vetter
2023-04-11 14:13 ` Daniel Vetter
2023-04-17 6:47 ` [Intel-xe] " Christian König
2023-04-17 6:47 ` Christian König
2023-04-17 8:39 ` [Intel-xe] " Daniel Vetter
2023-04-17 8:39 ` Daniel Vetter
2023-04-18 15:10 ` [Intel-xe] " Liviu Dudau
2023-04-18 15:10 ` Liviu Dudau
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=202304041537.dcZw4xgl-lkp@intel.com \
--to=lkp@intel.com \
--cc=matthew.brost@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.