From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, maarten.lankhorst@linux.intel.com,
matthew.auld@intel.com,
"Thomas Hellström" <thomas.hellstrom@intel.com>
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: Initial introduction of vma resources
Date: Wed, 27 Oct 2021 01:38:13 +0800 [thread overview]
Message-ID: <202110270147.eJC2sd9K-lkp@intel.com> (raw)
In-Reply-To: <20211026070744.337554-4-thomas.hellstrom@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]
Hi "Thomas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next airlied/drm-next v5.15-rc7 next-20211026]
[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/Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/6c17f33fae142e4401d64d5399eb28e3c68f13a1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
git checkout 6c17f33fae142e4401d64d5399eb28e3c68f13a1
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
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/i915/i915_vma.c:1519: warning: expecting prototype for i915_vma_resource_hold(). Prototype was for i915_vma_resource_unhold() instead
vim +1519 drivers/gpu/drm/i915/i915_vma.c
1508
1509 /**
1510 * i915_vma_resource_hold - Unhold the signaling of the vma resource unbind
1511 * fence.
1512 * @vma_res: The vma resource.
1513 * @lockdep_cookie: The lockdep cookie returned from i915_vma_resource_hold.
1514 *
1515 * The function may leave a dma_fence critical section.
1516 */
1517 void i915_vma_resource_unhold(struct i915_vma_resource *vma_res,
1518 bool lockdep_cookie)
> 1519 {
1520 dma_fence_end_signalling(lockdep_cookie);
1521
1522 if (IS_ENABLED(CONFIG_PROVE_LOCKING)) {
1523 unsigned long irq_flags;
1524
1525 /* Inefficient open-coded might_lock_irqsave() */
1526 spin_lock_irqsave(&vma_res->lock, irq_flags);
1527 spin_unlock_irqrestore(&vma_res->lock, irq_flags);
1528 }
1529
1530 __i915_vma_resource_unhold(vma_res);
1531 }
1532
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29897 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, maarten.lankhorst@linux.intel.com,
matthew.auld@intel.com,
"Thomas Hellström" <thomas.hellstrom@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: Initial introduction of vma resources
Date: Wed, 27 Oct 2021 01:38:13 +0800 [thread overview]
Message-ID: <202110270147.eJC2sd9K-lkp@intel.com> (raw)
In-Reply-To: <20211026070744.337554-4-thomas.hellstrom@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]
Hi "Thomas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next airlied/drm-next v5.15-rc7 next-20211026]
[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/Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/6c17f33fae142e4401d64d5399eb28e3c68f13a1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
git checkout 6c17f33fae142e4401d64d5399eb28e3c68f13a1
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
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/i915/i915_vma.c:1519: warning: expecting prototype for i915_vma_resource_hold(). Prototype was for i915_vma_resource_unhold() instead
vim +1519 drivers/gpu/drm/i915/i915_vma.c
1508
1509 /**
1510 * i915_vma_resource_hold - Unhold the signaling of the vma resource unbind
1511 * fence.
1512 * @vma_res: The vma resource.
1513 * @lockdep_cookie: The lockdep cookie returned from i915_vma_resource_hold.
1514 *
1515 * The function may leave a dma_fence critical section.
1516 */
1517 void i915_vma_resource_unhold(struct i915_vma_resource *vma_res,
1518 bool lockdep_cookie)
> 1519 {
1520 dma_fence_end_signalling(lockdep_cookie);
1521
1522 if (IS_ENABLED(CONFIG_PROVE_LOCKING)) {
1523 unsigned long irq_flags;
1524
1525 /* Inefficient open-coded might_lock_irqsave() */
1526 spin_lock_irqsave(&vma_res->lock, irq_flags);
1527 spin_unlock_irqrestore(&vma_res->lock, irq_flags);
1528 }
1529
1530 __i915_vma_resource_unhold(vma_res);
1531 }
1532
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29897 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 3/3] drm/i915: Initial introduction of vma resources
Date: Wed, 27 Oct 2021 01:38:13 +0800 [thread overview]
Message-ID: <202110270147.eJC2sd9K-lkp@intel.com> (raw)
In-Reply-To: <20211026070744.337554-4-thomas.hellstrom@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2627 bytes --]
Hi "Thomas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next airlied/drm-next v5.15-rc7 next-20211026]
[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/Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/6c17f33fae142e4401d64d5399eb28e3c68f13a1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Thomas-Hellstr-m/Prepare-error-capture-for-asynchronous-migration/20211026-150944
git checkout 6c17f33fae142e4401d64d5399eb28e3c68f13a1
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
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/i915/i915_vma.c:1519: warning: expecting prototype for i915_vma_resource_hold(). Prototype was for i915_vma_resource_unhold() instead
vim +1519 drivers/gpu/drm/i915/i915_vma.c
1508
1509 /**
1510 * i915_vma_resource_hold - Unhold the signaling of the vma resource unbind
1511 * fence.
1512 * @vma_res: The vma resource.
1513 * @lockdep_cookie: The lockdep cookie returned from i915_vma_resource_hold.
1514 *
1515 * The function may leave a dma_fence critical section.
1516 */
1517 void i915_vma_resource_unhold(struct i915_vma_resource *vma_res,
1518 bool lockdep_cookie)
> 1519 {
1520 dma_fence_end_signalling(lockdep_cookie);
1521
1522 if (IS_ENABLED(CONFIG_PROVE_LOCKING)) {
1523 unsigned long irq_flags;
1524
1525 /* Inefficient open-coded might_lock_irqsave() */
1526 spin_lock_irqsave(&vma_res->lock, irq_flags);
1527 spin_unlock_irqrestore(&vma_res->lock, irq_flags);
1528 }
1529
1530 __i915_vma_resource_unhold(vma_res);
1531 }
1532
---
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: 29897 bytes --]
next prev parent reply other threads:[~2021-10-26 17:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 7:07 [Intel-gfx] [PATCH 0/3] Prepare error capture for asynchronous migration Thomas Hellström
2021-10-26 7:07 ` Thomas Hellström
2021-10-26 7:07 ` [Intel-gfx] [PATCH 1/3] drm/i915: Introduce refcounted sg-tables Thomas Hellström
2021-10-26 7:07 ` Thomas Hellström
2021-10-26 7:07 ` [Intel-gfx] [PATCH 2/3] drm/i915: Update error capture code to avoid using the current vma state Thomas Hellström
2021-10-26 7:07 ` Thomas Hellström
2021-10-26 7:07 ` [Intel-gfx] [PATCH 3/3] drm/i915: Initial introduction of vma resources Thomas Hellström
2021-10-26 7:07 ` Thomas Hellström
2021-10-26 17:38 ` kernel test robot [this message]
2021-10-26 17:38 ` kernel test robot
2021-10-26 17:38 ` kernel test robot
2021-10-26 7:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prepare error capture for asynchronous migration Patchwork
2021-10-26 8:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-26 10:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=202110270147.eJC2sd9K-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
/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.