From: kbuild test robot <lkp@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [PATCH v2 4/4] drm/i915/selftests: Verify whitelist of context registers
Date: Wed, 17 Apr 2019 05:28:21 +0800 [thread overview]
Message-ID: <201904170527.bQV9HkIZ%lkp@intel.com> (raw)
In-Reply-To: <20190416081024.20536-4-chris@chris-wilson.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20190416]
[cannot apply to v5.1-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Verify-workarounds-immediately-after-application/20190417-035630
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-x017-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/intel_workarounds.c:1401:0:
drivers/gpu/drm/i915/selftests/intel_workarounds.c: In function 'neq_whitelisted_registers':
>> drivers/gpu/drm/i915/selftests/intel_workarounds.c:902:36: error: incompatible type for argument 2 of 'writeonly_reg'
!writeonly_reg(engine->i915, engine->whitelist.list[i])) {
^~~~~~
drivers/gpu/drm/i915/selftests/intel_workarounds.c:862:13: note: expected 'i915_reg_t {aka struct <anonymous>}' but argument is of type 'struct i915_wa'
static bool writeonly_reg(struct drm_i915_private *i915, i915_reg_t reg)
^~~~~~~~~~~~~
vim +/writeonly_reg +902 drivers/gpu/drm/i915/selftests/intel_workarounds.c
881
882 static int neq_whitelisted_registers(struct i915_vma *A,
883 struct i915_vma *B,
884 struct intel_engine_cs *engine)
885 {
886 u32 *a, *b;
887 int i, err;
888
889 a = i915_gem_object_pin_map(A->obj, I915_MAP_WB);
890 if (IS_ERR(a))
891 return PTR_ERR(a);
892
893 b = i915_gem_object_pin_map(B->obj, I915_MAP_WB);
894 if (IS_ERR(b)) {
895 err = PTR_ERR(b);
896 goto err_a;
897 }
898
899 err = 0;
900 for (i = 0; i < engine->whitelist.count; i++) {
901 if (a[i] == b[i] &&
> 902 !writeonly_reg(engine->i915, engine->whitelist.list[i])) {
903 pr_err("[%d] Whitelist register 0x%4x:%08x was unwritable\n",
904 i, i915_mmio_reg_offset(engine->whitelist.list[i].reg), a[i]);
905 err = -EINVAL;
906 }
907 }
908
909 i915_gem_object_unpin_map(B->obj);
910 err_a:
911 i915_gem_object_unpin_map(A->obj);
912 return err;
913 }
914
---
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: 27290 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-16 21:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 8:10 [PATCH v2 1/4] drm/i915: Verify workarounds immediately after application Chris Wilson
2019-04-16 8:10 ` [PATCH v2 2/4] drm/i915: Verify the engine workarounds stick on application Chris Wilson
2019-04-16 9:43 ` Tvrtko Ursulin
2019-04-16 9:57 ` Chris Wilson
2019-04-16 10:36 ` Tvrtko Ursulin
2019-04-16 10:49 ` Chris Wilson
2019-04-16 8:10 ` [PATCH v2 3/4] drm/i915: Make workaround verification *optional* Chris Wilson
2019-04-16 9:48 ` Tvrtko Ursulin
2019-04-16 11:24 ` Chris Wilson
2019-04-16 8:10 ` [PATCH v2 4/4] drm/i915/selftests: Verify whitelist of context registers Chris Wilson
2019-04-16 9:12 ` [PATCH] " Chris Wilson
2019-04-16 14:50 ` Tvrtko Ursulin
2019-04-24 10:00 ` Chris Wilson
2019-04-24 11:03 ` Chris Wilson
2019-04-24 11:10 ` Tvrtko Ursulin
2019-04-16 21:28 ` kbuild test robot [this message]
2019-04-16 9:18 ` [PATCH v2 1/4] drm/i915: Verify workarounds immediately after application Tvrtko Ursulin
2019-04-16 11:10 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: Verify workarounds immediately after application (rev2) Patchwork
2019-04-16 15:07 ` ✓ Fi.CI.IGT: " Patchwork
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=201904170527.bQV9HkIZ%lkp@intel.com \
--to=lkp@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox