From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Flush gen3 relocs harder, again
Date: Sat, 13 Jun 2020 11:44:39 +0300 [thread overview]
Message-ID: <87d063s6bs.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <159199981892.2981.2735577690762279899@build.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Mika Kuoppala (2020-06-12 23:05:18)
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>>
>> > gen3 does not fully flush MI stores to memory on MI_FLUSH, such that a
>> > subsequent read from e.g. the sampler can bypass the store and read the
>> > stale value from memory. This is a serious issue when we are using MI
>> > stores to rewrite the batches for relocation, as it means that the batch
>> > is reading from random user/kernel memory. While it is particularly
>> > sensitive [and detectable] for relocations, reading stale data at any
>> > time is a worry.
>> >
>> > Having started with a small number of delaying stores and doubling until
>> > no more incoherency was seen over a few hours (with and without
>> > background memory pressure), 32 was the magic number.
>> >
>> > v2: Follow more closer with the gen5 w/a and include some
>> > post-invalidate flushes as well.
>> >
>> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2018
>> > References: a889580c087a ("drm/i915: Flush GPU relocs harder for gen3")
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> > ---
>> > drivers/gpu/drm/i915/gt/gen2_engine_cs.c | 61 ++++++++++--------------
>> > 1 file changed, 25 insertions(+), 36 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/gt/gen2_engine_cs.c b/drivers/gpu/drm/i915/gt/gen2_engine_cs.c
>> > index 3fb0dc1fb910..5400d657f334 100644
>> > --- a/drivers/gpu/drm/i915/gt/gen2_engine_cs.c
>> > +++ b/drivers/gpu/drm/i915/gt/gen2_engine_cs.c
>> > @@ -13,28 +13,25 @@
>> >
>> > int gen2_emit_flush(struct i915_request *rq, u32 mode)
>> > {
>> > - unsigned int num_store_dw;
>> > + unsigned int num_store_dw = 12;
>> > u32 cmd, *cs;
>> >
>> > cmd = MI_FLUSH;
>> > - num_store_dw = 0;
>> > if (mode & EMIT_INVALIDATE)
>> > cmd |= MI_READ_FLUSH;
>> > - if (mode & EMIT_FLUSH)
>> > - num_store_dw = 4;
>> >
>> > - cs = intel_ring_begin(rq, 2 + 3 * num_store_dw);
>> > + cs = intel_ring_begin(rq, 2 + 4 * num_store_dw);
>> > if (IS_ERR(cs))
>> > return PTR_ERR(cs);
>> >
>> > *cs++ = cmd;
>> > while (num_store_dw--) {
>> > - *cs++ = MI_STORE_DWORD_IMM | MI_MEM_VIRTUAL;
>> > - *cs++ = intel_gt_scratch_offset(rq->engine->gt,
>> > - INTEL_GT_SCRATCH_FIELD_DEFAULT);
>> > - *cs++ = 0;
>> > + *cs++ = MI_STORE_DWORD_INDEX;
>> > + *cs++ = I915_GEM_HWS_SCRATCH * sizeof(u32);
>> > + *cs++ = rq->fence.seqno - 1;
>> > + *cs++ = MI_FLUSH | MI_NO_WRITE_FLUSH;
>> > }
>> > - *cs++ = MI_FLUSH | MI_NO_WRITE_FLUSH;
>> > + *cs++ = cmd;
>> >
>> > intel_ring_advance(rq, cs);
>> >
>> > @@ -142,38 +139,21 @@ int gen4_emit_flush_vcs(struct i915_request *rq, u32 mode)
>> > return 0;
>> > }
>> >
>> > -u32 *gen3_emit_breadcrumb(struct i915_request *rq, u32 *cs)
>> > +static u32 *__gen2_emit_breadcrumb(struct i915_request *rq, u32 *cs,
>> > + int flush, int post)
>> > {
>> > GEM_BUG_ON(i915_request_active_timeline(rq)->hwsp_ggtt != rq->engine->status_page.vma);
>> > GEM_BUG_ON(offset_in_page(i915_request_active_timeline(rq)->hwsp_offset) != I915_GEM_HWS_SEQNO_ADDR);
>> >
>> > *cs++ = MI_FLUSH;
>> >
>> > - *cs++ = MI_STORE_DWORD_INDEX;
>> > - *cs++ = I915_GEM_HWS_SEQNO_ADDR;
>> > - *cs++ = rq->fence.seqno;
>> > -
>> > - *cs++ = MI_USER_INTERRUPT;
>>
>> How can you throw the interrupt part out?
>
> Diff being confusing. gen3_emit_breadcrumb and gen5_emit_breadcrumb
> merged together.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-13 8:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:05 [Intel-gfx] [PATCH] drm/i915/gt: Flush gen3 relocs harder, again Chris Wilson
2020-06-11 16:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-06-11 16:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-11 21:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-06-12 9:14 ` [Intel-gfx] [PATCH] " Mika Kuoppala
2020-06-12 9:23 ` Chris Wilson
2020-06-12 9:40 ` Chris Wilson
2020-06-12 12:39 ` Chris Wilson
2020-06-12 22:05 ` Mika Kuoppala
2020-06-12 22:10 ` Chris Wilson
2020-06-13 8:44 ` Mika Kuoppala [this message]
2020-06-13 9:17 ` Chris Wilson
2020-06-12 13:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Flush gen3 relocs harder, again (rev2) Patchwork
2020-06-12 13:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-12 15:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=87d063s6bs.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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.