[Intel-gfx] [PATCH] drm/i915: Only report a wakeup if the waiter was truly asleep
kbuild test robot
lkp at intel.com
Wed Apr 5 10:40:30 UTC 2017
Hi Chris,
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20170405]
[cannot apply to v4.11-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-Only-report-a-wakeup-if-the-waiter-was-truly-asleep/20170405-165353
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-randconfig-x004-201714 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
drivers/gpu//drm/i915/intel_breadcrumbs.c: In function '__wake_up_sleeper':
>> drivers/gpu//drm/i915/intel_breadcrumbs.c:38:13: error: 'struct task_struct' has no member named 'on_cpu'; did you mean 'on_rq'?
return !tsk->on_cpu && wake_up_process(tsk);
^~
>> drivers/gpu//drm/i915/intel_breadcrumbs.c:39:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +38 drivers/gpu//drm/i915/intel_breadcrumbs.c
32 /* Be careful not to report a successful wakeup if the waiter is
33 * currently processing the seqno, where it will have already
34 * called set_task_state(TASK_INTERRUPTIBLE). We first check whether
35 * the task is currently asleep before calling ttwu, and then we
36 * only report success if we were the ones to then trigger the wakeup.
37 */
> 38 return !tsk->on_cpu && wake_up_process(tsk);
> 39 }
40
41 static unsigned int __intel_breadcrumbs_wakeup(struct intel_breadcrumbs *b)
42 {
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 28439 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gfx/attachments/20170405/9d00b43f/attachment-0001.gz>
More information about the Intel-gfx
mailing list