From: kbuild test robot <lkp@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
kbuild-all@01.org
Subject: Re: [PATCH] drm/i915: Annotate dma_fence waits
Date: Wed, 7 Nov 2018 00:48:56 +0800 [thread overview]
Message-ID: <201811070004.u5Yh3ltp%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181106135527.28354-1-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 2959 bytes --]
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v4.20-rc1 next-20181106]
[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/Daniel-Vetter/drm-i915-Annotate-dma_fence-waits/20181106-232827
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-x000-201844 (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 >>):
drivers/gpu//drm/i915/i915_request.c: In function 'i915_request_wait':
>> drivers/gpu//drm/i915/i915_request.c:1292:3: error: implicit declaration of function 'dma_fence_wait_acquire'; did you mean 'dma_fence_wait_timeout'? [-Werror=implicit-function-declaration]
dma_fence_wait_acquire();
^~~~~~~~~~~~~~~~~~~~~~
dma_fence_wait_timeout
>> drivers/gpu//drm/i915/i915_request.c:1295:3: error: implicit declaration of function 'dma_fence_wait_release'; did you mean 'dma_fence_release'? [-Werror=implicit-function-declaration]
dma_fence_wait_release();
^~~~~~~~~~~~~~~~~~~~~~
dma_fence_release
cc1: some warnings being treated as errors
vim +1292 drivers/gpu//drm/i915/i915_request.c
1265
1266 /**
1267 * i915_request_wait - wait until execution of request has finished
1268 * @rq: the request to wait upon
1269 * @flags: how to wait
1270 * @timeout: how long to wait in jiffies
1271 *
1272 * i915_request_wait() waits for the request to be completed, for a
1273 * maximum of @timeout jiffies (with MAX_SCHEDULE_TIMEOUT implying an
1274 * unbounded wait).
1275 *
1276 * If the caller holds the struct_mutex, the caller must pass I915_WAIT_LOCKED
1277 * in via the flags, and vice versa if the struct_mutex is not held, the caller
1278 * must not specify that the wait is locked.
1279 *
1280 * Returns the remaining time (in jiffies) if the request completed, which may
1281 * be zero or -ETIME if the request is unfinished after the timeout expires.
1282 * May return -EINTR is called with I915_WAIT_INTERRUPTIBLE and a signal is
1283 * pending before the request completes.
1284 */
1285 long i915_request_wait(struct i915_request *rq,
1286 unsigned int flags,
1287 long timeout)
1288 {
1289 long ret;
1290
1291 if (!lockdep_is_held(&rq->i915->drm.struct_mutex))
> 1292 dma_fence_wait_acquire();
1293 ret = __i915_request_wait(rq, flags, timeout);
1294 if (!lockdep_is_held(&rq->i915->drm.struct_mutex))
> 1295 dma_fence_wait_release();
1296
1297 return ret;
1298 }
1299
---
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: 33001 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-06 16:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:15 [PATCH 01/12] locking/lockdep: restore cross-release checks Daniel Vetter
2018-11-02 9:15 ` [PATCH 02/12] kthread: finer-grained lockdep/cross-release completion Daniel Vetter
2018-11-02 9:15 ` [PATCH 03/12] lockdep: Remove GFP_NOLOCKDEP annotation Daniel Vetter
2018-11-02 9:15 ` [PATCH 04/12] kernel/lockdep: Make cross-release a config option Daniel Vetter
2018-11-02 9:15 ` [PATCH 05/12] mm: Check if mmu notifier callbacks are allowed to fail Daniel Vetter
2018-11-02 9:15 ` [PATCH 06/12] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2018-11-02 9:15 ` [PATCH 07/12] mm, notifier: Add a lockdep map for invalidate_range_start Daniel Vetter
2018-11-02 9:15 ` [PATCH 08/12] dma-fence: cross-release annotations Daniel Vetter
2018-11-02 9:15 ` [PATCH 09/12] reservation: Annotate dma_fence waits Daniel Vetter
2018-11-02 9:15 ` [PATCH 10/12] drm/i915: " Daniel Vetter
2018-11-06 13:55 ` [PATCH] " Daniel Vetter
2018-11-06 16:48 ` kbuild test robot [this message]
2018-11-06 16:48 ` kbuild test robot
2018-11-02 9:15 ` [PATCH 11/12] drm/i915: annotate intel_atomic_commit_fence_wait Daniel Vetter
2018-11-02 9:15 ` [PATCH 12/12] HAX FOR CI: Enable cross-release Daniel Vetter
2018-11-02 9:43 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/12] locking/lockdep: restore cross-release checks Patchwork
2018-11-02 9:49 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-02 10:04 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-06 14:14 ` ✗ Fi.CI.BAT: failure for series starting with [01/12] locking/lockdep: restore cross-release checks (rev2) Patchwork
2018-11-06 15:05 ` [PATCH] locking/lockdep: restore cross-release checks Daniel Vetter
2018-11-06 15:50 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with locking/lockdep: restore cross-release checks (rev3) Patchwork
2018-11-06 15:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-07 9:14 ` ✗ Fi.CI.BAT: 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=201811070004.u5Yh3ltp%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 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.