All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 9/9] i915/gem_ctx_engine: Drip feed requests into 'independent'
Date: Tue, 13 Aug 2019 18:37:41 +0300	[thread overview]
Message-ID: <20190813153741.GC32007@intel.intel> (raw)
In-Reply-To: <20190813062016.7870-9-chris@chris-wilson.co.uk>

Hi Chris,

On Tue, Aug 13, 2019 at 07:20:16AM +0100, Chris Wilson wrote:
> The intent of the test is to exercise that each channel in the engine[]
> is an independent context/ring/timeline. It setups 64 channels pointing
> to rcs0 and then submits one request to each in turn waiting on a
> timeline that will force them to run out of submission order. They can
> only run in fence order and not submission order if the timelines of
> each channel are truly independent.
> 
> However, we released the fences en masse, and once the requests are
> ready they are independent any may be executed in any order by the HW,

typo here

> especially true with timeslicing that may reorder the requests on a
> whim. So instead of releasing all requests at once, increment the
> timeline step by step and check we get our results advancing. If the
> requests can not be run in fence order and fall back to submission
> order, we will time out waiting for our incremental results and trigger
> a few GPU hangs.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110987
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Looks OK.

Reviewed-by: Andi Shyti <andi.shyti@intel.com>

Thanks,
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 9/9] i915/gem_ctx_engine: Drip feed requests into 'independent'
Date: Tue, 13 Aug 2019 18:37:41 +0300	[thread overview]
Message-ID: <20190813153741.GC32007@intel.intel> (raw)
In-Reply-To: <20190813062016.7870-9-chris@chris-wilson.co.uk>

Hi Chris,

On Tue, Aug 13, 2019 at 07:20:16AM +0100, Chris Wilson wrote:
> The intent of the test is to exercise that each channel in the engine[]
> is an independent context/ring/timeline. It setups 64 channels pointing
> to rcs0 and then submits one request to each in turn waiting on a
> timeline that will force them to run out of submission order. They can
> only run in fence order and not submission order if the timelines of
> each channel are truly independent.
> 
> However, we released the fences en masse, and once the requests are
> ready they are independent any may be executed in any order by the HW,

typo here

> especially true with timeslicing that may reorder the requests on a
> whim. So instead of releasing all requests at once, increment the
> timeline step by step and check we get our results advancing. If the
> requests can not be run in fence order and fall back to submission
> order, we will time out waiting for our incremental results and trigger
> a few GPU hangs.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110987
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Looks OK.

Reviewed-by: Andi Shyti <andi.shyti@intel.com>

Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-08-13 15:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13  6:20 [igt-dev] [PATCH i-g-t 1/9] i915/gem_exec_schedule: Limit the plug to fit small rings Chris Wilson
2019-08-13  6:20 ` Chris Wilson
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 2/9] i915/gem_eio: Restrict number of batches of submitted Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13 14:21   ` [igt-dev] [Intel-gfx] " Andi Shyti
2019-08-13 14:21     ` Andi Shyti
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 3/9] i915/gem_mmap_gtt: Test mmap_offset lifetime Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 4/9] i915/gem_shrink: Make some pages dirty Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13 15:37   ` [igt-dev] " Andi Shyti
2019-08-13 15:37     ` Andi Shyti
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 5/9] i915/gem_userptr_blits: Apply some THP pressure Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13 15:37   ` [Intel-gfx] [igt-dev] " Andi Shyti
2019-08-13 15:37     ` Andi Shyti
2019-08-13  6:20 ` [Intel-gfx] [PATCH i-g-t 6/9] i915/gem_exec_schedule: Check timeslice Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 7/9] i915/perf_pmu: Flush idle work before waiting for suspend Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 8/9] Force spin-batch to cause a hang as required Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13  6:20 ` [igt-dev] [PATCH i-g-t 9/9] i915/gem_ctx_engine: Drip feed requests into 'independent' Chris Wilson
2019-08-13  6:20   ` Chris Wilson
2019-08-13 15:37   ` Andi Shyti [this message]
2019-08-13 15:37     ` [igt-dev] " Andi Shyti
2019-08-13  7:22 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/9] i915/gem_exec_schedule: Limit the plug to fit small rings Patchwork
2019-08-13 14:20 ` [igt-dev] [PATCH i-g-t 1/9] " Andi Shyti
2019-08-13 14:20   ` Andi Shyti

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=20190813153741.GC32007@intel.intel \
    --to=andi.shyti@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --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 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.