From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
intel-gfx@lists.freedesktop.org, imre.deak@intel.com
Subject: Re: [PATCH] drm/i915: avoid leaking DMA mappings
Date: 07 Jul 2015 12:09:48 -0700 [thread overview]
Message-ID: <acb6cf$milbp8@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1436194237-850-1-git-send-email-imre.deak@intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6732
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
ILK -4 302/302 298/302
SNB -4 312/316 308/316
IVB -5 345/345 340/345
BYT -1 289/289 288/289
HSW -5 382/382 377/382
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*ILK igt@gem_userptr_blits@dmabuf-sync PASS(1) FAIL(1)
*ILK igt@gem_userptr_blits@dmabuf-unsync PASS(1) FAIL(1)
*ILK igt@gem_userptr_blits@forked-access PASS(1) FAIL(1)
*ILK igt@gem_userptr_blits@forked-sync-interruptible PASS(1) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem_userptr.c:#cancel_userptr[i915]()@WARNING:.* at .* cancel_userptr+0x
*SNB igt@gem_userptr_blits@coherency-sync PASS(1) CRASH(1)
*SNB igt@gem_userptr_blits@dmabuf-sync PASS(1) FAIL(1)
*SNB igt@gem_userptr_blits@dmabuf-unsync PASS(1) FAIL(1)
*SNB igt@gem_userptr_blits@forked-access PASS(1) FAIL(1)
*IVB igt@gem_userptr_blits@coherency-sync PASS(1) CRASH(1)
*IVB igt@gem_userptr_blits@coherency-unsync PASS(1) CRASH(1)
*IVB igt@gem_userptr_blits@dmabuf-sync PASS(1) FAIL(1)
*IVB igt@gem_userptr_blits@dmabuf-unsync PASS(1) FAIL(1)
*IVB igt@gem_userptr_blits@forked-access PASS(1) FAIL(1)
*BYT igt@gem_userptr_blits@forked-access PASS(1) FAIL(1)
*HSW igt@gem_userptr_blits@coherency-sync PASS(1) FAIL(1)
*HSW igt@gem_userptr_blits@coherency-unsync PASS(1) FAIL(1)
*HSW igt@gem_userptr_blits@dmabuf-sync PASS(1) FAIL(1)
*HSW igt@gem_userptr_blits@dmabuf-unsync PASS(1) FAIL(1)
*HSW igt@gem_userptr_blits@forked-access PASS(1) FAIL(1)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-07 19:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:50 [PATCH] drm/i915: avoid leaking DMA mappings Imre Deak
2015-07-06 14:57 ` Chris Wilson
2015-07-06 15:11 ` Imre Deak
2015-07-06 15:28 ` Chris Wilson
2015-07-06 15:31 ` Imre Deak
2015-07-06 15:29 ` Daniel Vetter
2015-07-06 15:30 ` Imre Deak
2015-07-06 15:33 ` Chris Wilson
2015-07-06 15:56 ` Imre Deak
2015-07-06 16:04 ` Chris Wilson
2015-07-06 16:23 ` Imre Deak
2015-07-06 15:11 ` Tvrtko Ursulin
2015-07-06 15:21 ` Imre Deak
2015-07-07 19:09 ` shuang.he [this message]
2015-07-08 16:18 ` [PATCH v2 1/2] " Imre Deak
2015-07-08 17:19 ` Chris Wilson
2015-07-09 9:59 ` [PATCH v3 " Imre Deak
2015-07-09 10:04 ` Chris Wilson
2015-07-11 20:54 ` Chris Wilson
2015-07-13 12:15 ` Imre Deak
2015-07-08 16:18 ` [PATCH 2/2] drm/i915: remove unused has_dma_mapping flag Imre Deak
2015-07-08 17:43 ` Chris Wilson
2015-07-13 14:46 ` Daniel Vetter
2015-07-09 0:07 ` shuang.he
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='acb6cf$milbp8@fmsmga002.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lei.a.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox