From: Daniel Vetter <daniel@ffwll.ch>
To: bradley.d.volkin@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 0/5] Command parser batch buffer copy
Date: Tue, 4 Nov 2014 11:31:29 +0100 [thread overview]
Message-ID: <20141104103129.GI26941@phenom.ffwll.local> (raw)
In-Reply-To: <1415042385-26445-1-git-send-email-bradley.d.volkin@intel.com>
On Mon, Nov 03, 2014 at 11:19:40AM -0800, bradley.d.volkin@intel.com wrote:
> From: Brad Volkin <bradley.d.volkin@intel.com>
>
> This is v3 of the series I sent here:
> http://lists.freedesktop.org/archives/intel-gfx/2014-July/048705.html
>
> Most of the previous commentary still applies. We've fixed the secure
> dispatch regression though, so the series now puts the parser into
> enabling mode in patch 2.
>
> There are currently some regressions. I've sent i-g-t patches for a couple that
> are test issues. The remaining issues are:
>
> drv_hangman error-state-capture-*
> The test has checks that the logged 'gtt_offset' matches the expected
> offset of the userspace-supplied batch buffer. Similarly for the address
> in an MI_BATCH_BUFFER_START command found in the logged ringbuffer contents.
> These obviously won't match if the buffer submitted to hardware is from the
> batch pool instead of the one from userspace.
>
> gem_reloc_vs_gpu *-thrash-inactive
> gem_persistent_relocs *-thrash-inactive
> These fail with this type of error:
>
> Test assertion failure function do_test, file gem_reloc_vs_gpu.c:221:
> Failed assertion: test == 0xdeadbeef
> mismatch in buffer 0: 0x00000000 instead of 0xdeadbeef
> child 6 failed with exit status 99
> Subtest forked-thrash-inactive: FAIL (3.824s)
>
> One crashed, apparently in i915_gem_object_move_to_inactive() called via
> i915_gem_reset(). I assume there's an issue with my active tracking or
> madv usage for batch pool objects. Any input would be helpful.
>
> gem_cs_tlb
> This test takes longer and may time out.
>
> Brad Volkin (5):
> drm/i915: Implement a framework for batch buffer pools
> drm/i915: Use batch pools with the command parser
> drm/i915: Add a batch pool debugfs file
> drm/i915: Add batch pool details to i915_gem_objects debugfs
> drm/i915: Use batch length instead of object size in command parser
Looks good overall, some comments on the 2nd patch. With those addressed
imo ready for detailed review.
Cheers, Daniel
>
> Documentation/DocBook/drm.tmpl | 5 +
> drivers/gpu/drm/i915/Makefile | 1 +
> drivers/gpu/drm/i915/i915_cmd_parser.c | 102 +++++++++++++++----
> drivers/gpu/drm/i915/i915_debugfs.c | 86 ++++++++++++++--
> drivers/gpu/drm/i915/i915_dma.c | 1 +
> drivers/gpu/drm/i915/i915_drv.h | 26 +++++
> drivers/gpu/drm/i915/i915_gem.c | 11 +++
> drivers/gpu/drm/i915/i915_gem_batch_pool.c | 153 +++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 62 +++++++++++-
> 9 files changed, 416 insertions(+), 31 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/i915_gem_batch_pool.c
>
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-11-04 10:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 19:19 [PATCH v3 0/5] Command parser batch buffer copy bradley.d.volkin
2014-11-03 19:19 ` [PATCH v3 1/5] drm/i915: Implement a framework for batch buffer pools bradley.d.volkin
2014-11-03 19:19 ` [PATCH v3 2/5] drm/i915: Use batch pools with the command parser bradley.d.volkin
2014-11-04 10:17 ` Daniel Vetter
2014-11-04 16:35 ` Volkin, Bradley D
2014-11-05 9:50 ` Daniel Vetter
2014-11-05 10:20 ` Daniel Vetter
2014-11-05 22:42 ` Volkin, Bradley D
2014-11-06 7:36 ` Chris Wilson
2014-11-06 13:56 ` Daniel Vetter
2014-11-06 17:38 ` Volkin, Bradley D
2014-11-07 9:32 ` Chris Wilson
2014-11-07 9:45 ` Daniel Vetter
2014-11-04 10:30 ` Daniel Vetter
2014-11-04 16:46 ` Volkin, Bradley D
2014-11-05 9:53 ` Daniel Vetter
2014-11-03 19:19 ` [PATCH v3 3/5] drm/i915: Add a batch pool debugfs file bradley.d.volkin
2014-11-03 19:19 ` [PATCH v3 4/5] drm/i915: Add batch pool details to i915_gem_objects debugfs bradley.d.volkin
2014-11-03 19:19 ` [PATCH v3 5/5] drm/i915: Use batch length instead of object size in command parser bradley.d.volkin
2014-11-03 19:32 ` [PATCH v3 5/5] drm/i915: Use batch length instead of shuang.he
2014-11-03 22:44 ` [PATCH v3 0/5] Command parser batch buffer copy Volkin, Bradley D
2014-11-04 9:51 ` Daniel Vetter
2014-11-04 10:31 ` Daniel Vetter [this message]
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=20141104103129.GI26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=bradley.d.volkin@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox