From: kbuild test robot <lkp@intel.com>
To: Nick Hoath <nicholas.hoath@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [PATCH] drm/i915: Change context lifecycle
Date: Wed, 25 Nov 2015 00:41:10 +0800 [thread overview]
Message-ID: <201511250046.OTVKdKFU%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448382236-36551-1-git-send-email-nicholas.hoath@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
Hi Nick,
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v4.4-rc2 next-20151124]
url: https://github.com/0day-ci/linux/commits/Nick-Hoath/drm-i915-Change-context-lifecycle/20151125-002840
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-randconfig-x019-11241713 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
drivers/gpu/drm/i915/intel_lrc.c: In function 'intel_lr_context_free':
>> drivers/gpu/drm/i915/intel_lrc.c:2404:6: warning: ignoring return value of 'i915_wait_request', declared with attribute warn_unused_result [-Wunused-result]
i915_wait_request(req);
^
drivers/gpu/drm/i915/intel_lrc.c: In function 'intel_logical_ring_begin':
drivers/gpu/drm/i915/intel_lrc.c:711:17: warning: 'space' may be used uninitialized in this function [-Wmaybe-uninitialized]
ringbuf->space = space;
^
drivers/gpu/drm/i915/intel_lrc.c:679:11: note: 'space' was declared here
unsigned space;
^
vim +/i915_wait_request +2404 drivers/gpu/drm/i915/intel_lrc.c
2388 ctx->engine[i].ringbuf;
2389 struct intel_engine_cs *ring = ringbuf->ring;
2390
2391 if (ctx == ring->default_context) {
2392 intel_unpin_ringbuffer_obj(ringbuf);
2393 i915_gem_object_ggtt_unpin(ctx_obj);
2394 }
2395
2396 if (ctx->engine[ring->id].unsaved) {
2397 int ret;
2398 struct drm_i915_gem_request *req;
2399
2400 ret = i915_gem_request_alloc(ring,
2401 ring->default_context, &req);
2402 if (!ret) {
2403 i915_add_request(req);
> 2404 i915_wait_request(req);
2405 }
2406 }
2407
2408 WARN_ON(ctx->engine[i].pin_count);
2409 intel_ringbuffer_free(ringbuf);
2410 drm_gem_object_unreference(&ctx_obj->base);
2411 }
2412 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 22620 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-24 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 16:23 [PATCH] drm/i915: Change context lifecycle Nick Hoath
2015-11-24 16:41 ` kbuild test robot [this message]
2015-11-25 1:11 ` Yu Dai
2015-11-25 12:52 ` Nick Hoath
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 12:57 Nick Hoath
2015-11-25 15:02 ` Mika Kuoppala
2015-11-25 20:27 ` Yu Dai
2015-11-26 8:48 ` Daniel Vetter
2015-11-26 9:19 ` Nick Hoath
2015-11-26 10:08 ` Daniel Vetter
2015-11-25 18:34 ` Yu Dai
2015-11-09 16:18 Nick Hoath
2015-11-10 8:49 ` Chris Wilson
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=201511250046.OTVKdKFU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=nicholas.hoath@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.