From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [RFC PATCH 1/1] drm/mm: add ig_frag selftest
Date: Mon, 01 Jun 2020 06:29:45 +0800 [thread overview]
Message-ID: <202006010625.2czQpxJF%lkp@intel.com> (raw)
In-Reply-To: <20200529163351.5228-1-nirmoy.das@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2615 bytes --]
Hi Nirmoy,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next linus/master v5.7-rc7 next-20200529]
[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/Nirmoy-Das/drm-mm-add-ig_frag-selftest/20200601-005135
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: arc-randconfig-m031-20200531 (attached as .config)
compiler: arc-elf-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
smatch warnings:
drivers/gpu/drm/selftests/test-drm_mm.c:1084 igt_frag() warn: unsigned 'insert_time1' is never less than zero.
drivers/gpu/drm/selftests/test-drm_mm.c:1088 igt_frag() warn: unsigned 'insert_time2' is never less than zero.
vim +/insert_time1 +1084 drivers/gpu/drm/selftests/test-drm_mm.c
1069
1070 static int igt_frag(void *ignored)
1071 {
1072 const struct insert_mode *mode;
1073 unsigned int insert_time1, insert_time2;
1074 unsigned int insert_size = 10000;
1075 unsigned int scale_factor = 4;
1076 /* tolerate 10% excess insertion duration */
1077 unsigned int error_factor = 110;
1078 int ret = -EINVAL;
1079
1080 for (mode = insert_modes; mode->name; mode++) {
1081 unsigned int expected_time;
1082
1083 insert_time1 = get_insert_time(insert_size, mode);
> 1084 if (insert_time1 < 0)
1085 goto err;
1086
1087 insert_time2 = get_insert_time((insert_size * 2), mode);
> 1088 if (insert_time2 < 0)
1089 goto err;
1090
1091 expected_time = (scale_factor * insert_time1 *
1092 error_factor)/100;
1093 if (insert_time2 > expected_time) {
1094 pr_err("%s fragmented insert took more %u msecs\n",
1095 mode->name, insert_time2 - expected_time);
1096 goto err;
1097 }
1098
1099 pr_info("%s fragmented insert of %u and %u insertions took %u and %u msecs\n",
1100 mode->name, insert_size, insert_size * 2, insert_time1,
1101 insert_time2);
1102 }
1103
1104 ret = 0;
1105 err:
1106 return ret;
1107 }
1108
---
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: 28111 bytes --]
next prev parent reply other threads:[~2020-05-31 22:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 16:33 [RFC PATCH 1/1] drm/mm: add ig_frag selftest Nirmoy Das
2020-05-29 16:33 ` [Intel-gfx] " Nirmoy Das
2020-05-29 15:40 ` Nirmoy
2020-05-29 15:40 ` [Intel-gfx] " Nirmoy
2020-05-29 15:52 ` Chris Wilson
2020-05-29 15:52 ` [Intel-gfx] " Chris Wilson
2020-05-29 21:01 ` Nirmoy
2020-05-29 21:01 ` [Intel-gfx] " Nirmoy
2020-06-02 12:47 ` Christian König
2020-06-02 12:47 ` [Intel-gfx] " Christian König
2020-06-02 14:13 ` Nirmoy
2020-06-02 14:13 ` [Intel-gfx] " Nirmoy
2020-06-02 14:25 ` Christian König
2020-06-02 14:25 ` [Intel-gfx] " Christian König
2020-06-03 9:10 ` Nirmoy
2020-06-03 9:10 ` [Intel-gfx] " Nirmoy
2020-05-29 22:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [RFC,1/1] " Patchwork
2020-05-29 23:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-30 3:20 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-05-31 22:29 ` kbuild test robot [this message]
2020-06-01 3:07 ` [Intel-gfx] [RFC PATCH 1/1] " kbuild test robot
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=202006010625.2czQpxJF%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.