* [PATCH] drm/i915: Remove Braswell GGTT update w/a
@ 2017-02-20 12:47 Chris Wilson
2017-02-20 13:52 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-02-22 11:27 ` [PATCH] " Joonas Lahtinen
0 siblings, 2 replies; 7+ messages in thread
From: Chris Wilson @ 2017-02-20 12:47 UTC (permalink / raw)
To: intel-gfx; +Cc: Daniel Vetter
Testing with concurrent GGTT accesses no longer show the coherency
problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
to GGTT with access through GGTT on Braswell"). My presumption is that
the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
Wait for writes through the GTT to land before reading back"), along
with the use of WC updates to the global gTT in commit 8448661d65f6
("drm/i915: Convert clflushed pagetables over to WC maps". Given
that the original symptoms can no longer be reproduced, time to remove
the workaround.
Testcase: igt/gem_concurrenct_blit
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
---
drivers/gpu/drm/i915/i915_gem_gtt.c | 28 ----------------------------
1 file changed, 28 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
index 18c051a11b7d..8302dae0b9c6 100644
--- a/drivers/gpu/drm/i915/i915_gem_gtt.c
+++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
@@ -2085,32 +2085,6 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,
ggtt->invalidate(vm->i915);
}
-struct insert_entries {
- struct i915_address_space *vm;
- struct sg_table *st;
- u64 start;
- enum i915_cache_level level;
- u32 flags;
-};
-
-static int gen8_ggtt_insert_entries__cb(void *_arg)
-{
- struct insert_entries *arg = _arg;
- gen8_ggtt_insert_entries(arg->vm, arg->st,
- arg->start, arg->level, arg->flags);
- return 0;
-}
-
-static void gen8_ggtt_insert_entries__BKL(struct i915_address_space *vm,
- struct sg_table *st,
- u64 start,
- enum i915_cache_level level,
- u32 flags)
-{
- struct insert_entries arg = { vm, st, start, level, flags };
- stop_machine(gen8_ggtt_insert_entries__cb, &arg, NULL);
-}
-
static void gen6_ggtt_insert_page(struct i915_address_space *vm,
dma_addr_t addr,
u64 offset,
@@ -2762,8 +2736,6 @@ static int gen8_gmch_probe(struct i915_ggtt *ggtt)
ggtt->base.clear_range = gen8_ggtt_clear_range;
ggtt->base.insert_entries = gen8_ggtt_insert_entries;
- if (IS_CHERRYVIEW(dev_priv))
- ggtt->base.insert_entries = gen8_ggtt_insert_entries__BKL;
ggtt->invalidate = gen6_ggtt_invalidate;
--
2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 7+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915: Remove Braswell GGTT update w/a
2017-02-20 12:47 [PATCH] drm/i915: Remove Braswell GGTT update w/a Chris Wilson
@ 2017-02-20 13:52 ` Patchwork
2017-02-22 11:27 ` [PATCH] " Joonas Lahtinen
1 sibling, 0 replies; 7+ messages in thread
From: Patchwork @ 2017-02-20 13:52 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Remove Braswell GGTT update w/a
URL : https://patchwork.freedesktop.org/series/19942/
State : success
== Summary ==
Series 19942v1 drm/i915: Remove Braswell GGTT update w/a
https://patchwork.freedesktop.org/api/1.0/series/19942/revisions/1/mbox/
fi-bdw-5557u total:252 pass:241 dwarn:0 dfail:0 fail:0 skip:11
fi-bsw-n3050 total:252 pass:213 dwarn:0 dfail:0 fail:0 skip:39
fi-bxt-j4205 total:252 pass:233 dwarn:0 dfail:0 fail:0 skip:19
fi-bxt-t5700 total:83 pass:70 dwarn:0 dfail:0 fail:0 skip:12
fi-byt-j1900 total:252 pass:225 dwarn:0 dfail:0 fail:0 skip:27
fi-byt-n2820 total:252 pass:221 dwarn:0 dfail:0 fail:0 skip:31
fi-hsw-4770 total:252 pass:236 dwarn:0 dfail:0 fail:0 skip:16
fi-hsw-4770r total:252 pass:236 dwarn:0 dfail:0 fail:0 skip:16
fi-ilk-650 total:252 pass:202 dwarn:0 dfail:0 fail:0 skip:50
fi-ivb-3520m total:252 pass:234 dwarn:0 dfail:0 fail:0 skip:18
fi-ivb-3770 total:252 pass:234 dwarn:0 dfail:0 fail:0 skip:18
fi-kbl-7500u total:252 pass:234 dwarn:0 dfail:0 fail:0 skip:18
fi-skl-6260u total:252 pass:242 dwarn:0 dfail:0 fail:0 skip:10
fi-skl-6700hq total:252 pass:235 dwarn:0 dfail:0 fail:0 skip:17
fi-skl-6700k total:252 pass:230 dwarn:4 dfail:0 fail:0 skip:18
fi-skl-6770hq total:252 pass:242 dwarn:0 dfail:0 fail:0 skip:10
fi-snb-2520m total:252 pass:224 dwarn:0 dfail:0 fail:0 skip:28
fi-snb-2600 total:252 pass:223 dwarn:0 dfail:0 fail:0 skip:29
45a2990174f3cf4dfa5d07b204d17b11d6a7410a drm-tip: 2017y-02m-20d-12h-54m-53s UTC integration manifest
92a894d drm/i915: Remove Braswell GGTT update w/a
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3898/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] drm/i915: Remove Braswell GGTT update w/a
2017-02-20 12:47 [PATCH] drm/i915: Remove Braswell GGTT update w/a Chris Wilson
2017-02-20 13:52 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2017-02-22 11:27 ` Joonas Lahtinen
2017-02-22 11:39 ` Chris Wilson
2017-02-23 9:33 ` Chris Wilson
1 sibling, 2 replies; 7+ messages in thread
From: Joonas Lahtinen @ 2017-02-22 11:27 UTC (permalink / raw)
To: Chris Wilson, intel-gfx; +Cc: Daniel Vetter
On ma, 2017-02-20 at 12:47 +0000, Chris Wilson wrote:
> Testing with concurrent GGTT accesses no longer show the coherency
> problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
> to GGTT with access through GGTT on Braswell"). My presumption is that
> the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
> Wait for writes through the GTT to land before reading back"), along
> with the use of WC updates to the global gTT in commit 8448661d65f6
> ("drm/i915: Convert clflushed pagetables over to WC maps". Given
> that the original symptoms can no longer be reproduced, time to remove
> the workaround.
>
> Testcase: igt/gem_concurrenct_blit
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Makes one think if the original fix has been appropriate, when adding
stop_machine for a software bug :P
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] drm/i915: Remove Braswell GGTT update w/a
2017-02-22 11:27 ` [PATCH] " Joonas Lahtinen
@ 2017-02-22 11:39 ` Chris Wilson
2017-02-22 18:02 ` Chris Wilson
2017-02-23 9:33 ` Chris Wilson
1 sibling, 1 reply; 7+ messages in thread
From: Chris Wilson @ 2017-02-22 11:39 UTC (permalink / raw)
To: Joonas Lahtinen; +Cc: Daniel Vetter, intel-gfx
On Wed, Feb 22, 2017 at 01:27:41PM +0200, Joonas Lahtinen wrote:
> On ma, 2017-02-20 at 12:47 +0000, Chris Wilson wrote:
> > Testing with concurrent GGTT accesses no longer show the coherency
> > problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
> > to GGTT with access through GGTT on Braswell"). My presumption is that
> > the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
> > Wait for writes through the GTT to land before reading back"), along
> > with the use of WC updates to the global gTT in commit 8448661d65f6
> > ("drm/i915: Convert clflushed pagetables over to WC maps". Given
> > that the original symptoms can no longer be reproduced, time to remove
> > the workaround.
> >
> > Testcase: igt/gem_concurrenct_blit
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Makes one think if the original fix has been appropriate, when adding
> stop_machine for a software bug :P
Depends if you consider the months of hair pulling trying to find where
the flush/stall was missing. It was a desperate patch to fix an annoying
corruption issue - and since it seems that we now just avoid the
dangerous path by taking a different route through hw, I don't think
it is was wholly a sw bug.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] drm/i915: Remove Braswell GGTT update w/a
2017-02-22 11:39 ` Chris Wilson
@ 2017-02-22 18:02 ` Chris Wilson
2017-02-22 23:04 ` Chris Wilson
0 siblings, 1 reply; 7+ messages in thread
From: Chris Wilson @ 2017-02-22 18:02 UTC (permalink / raw)
To: Joonas Lahtinen, intel-gfx, Daniel Vetter
On Wed, Feb 22, 2017 at 11:39:30AM +0000, Chris Wilson wrote:
> On Wed, Feb 22, 2017 at 01:27:41PM +0200, Joonas Lahtinen wrote:
> > On ma, 2017-02-20 at 12:47 +0000, Chris Wilson wrote:
> > > Testing with concurrent GGTT accesses no longer show the coherency
> > > problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
> > > to GGTT with access through GGTT on Braswell"). My presumption is that
> > > the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
> > > Wait for writes through the GTT to land before reading back"), along
> > > with the use of WC updates to the global gTT in commit 8448661d65f6
> > > ("drm/i915: Convert clflushed pagetables over to WC maps". Given
> > > that the original symptoms can no longer be reproduced, time to remove
> > > the workaround.
> > >
> > > Testcase: igt/gem_concurrenct_blit
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> >
> > Makes one think if the original fix has been appropriate, when adding
> > stop_machine for a software bug :P
>
> Depends if you consider the months of hair pulling trying to find where
> the flush/stall was missing. It was a desperate patch to fix an annoying
> corruption issue - and since it seems that we now just avoid the
> dangerous path by taking a different route through hw, I don't think
> it is was wholly a sw bug.
Bah, after a few days of continuous testing, I've hit a workload that
shows the bug again. (Small numbers of large GTT objects, rather than
large number of small GTT objects.)
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] drm/i915: Remove Braswell GGTT update w/a
2017-02-22 18:02 ` Chris Wilson
@ 2017-02-22 23:04 ` Chris Wilson
0 siblings, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2017-02-22 23:04 UTC (permalink / raw)
To: Joonas Lahtinen, intel-gfx, Daniel Vetter
On Wed, Feb 22, 2017 at 06:02:46PM +0000, Chris Wilson wrote:
> On Wed, Feb 22, 2017 at 11:39:30AM +0000, Chris Wilson wrote:
> > On Wed, Feb 22, 2017 at 01:27:41PM +0200, Joonas Lahtinen wrote:
> > > On ma, 2017-02-20 at 12:47 +0000, Chris Wilson wrote:
> > > > Testing with concurrent GGTT accesses no longer show the coherency
> > > > problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
> > > > to GGTT with access through GGTT on Braswell"). My presumption is that
> > > > the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
> > > > Wait for writes through the GTT to land before reading back"), along
> > > > with the use of WC updates to the global gTT in commit 8448661d65f6
> > > > ("drm/i915: Convert clflushed pagetables over to WC maps". Given
> > > > that the original symptoms can no longer be reproduced, time to remove
> > > > the workaround.
> > > >
> > > > Testcase: igt/gem_concurrenct_blit
> > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > >
> > > Makes one think if the original fix has been appropriate, when adding
> > > stop_machine for a software bug :P
> >
> > Depends if you consider the months of hair pulling trying to find where
> > the flush/stall was missing. It was a desperate patch to fix an annoying
> > corruption issue - and since it seems that we now just avoid the
> > dangerous path by taking a different route through hw, I don't think
> > it is was wholly a sw bug.
>
> Bah, after a few days of continuous testing, I've hit a workload that
> shows the bug again. (Small numbers of large GTT objects, rather than
> large number of small GTT objects.)
Hmm, and it also died with the w/a with nigh on identical symptoms. And
appears quite tempermental. Uncertainity is prevailing.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] drm/i915: Remove Braswell GGTT update w/a
2017-02-22 11:27 ` [PATCH] " Joonas Lahtinen
2017-02-22 11:39 ` Chris Wilson
@ 2017-02-23 9:33 ` Chris Wilson
1 sibling, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2017-02-23 9:33 UTC (permalink / raw)
To: Joonas Lahtinen; +Cc: Daniel Vetter, intel-gfx
On Wed, Feb 22, 2017 at 01:27:41PM +0200, Joonas Lahtinen wrote:
> On ma, 2017-02-20 at 12:47 +0000, Chris Wilson wrote:
> > Testing with concurrent GGTT accesses no longer show the coherency
> > problems from yonder, commit 5bab6f60cb4d ("drm/i915: Serialise updates
> > to GGTT with access through GGTT on Braswell"). My presumption is that
> > the root cause was more likely fixed by commit 3b5724d702ef ("drm/i915:
> > Wait for writes through the GTT to land before reading back"), along
> > with the use of WC updates to the global gTT in commit 8448661d65f6
> > ("drm/i915: Convert clflushed pagetables over to WC maps". Given
> > that the original symptoms can no longer be reproduced, time to remove
> > the workaround.
> >
> > Testcase: igt/gem_concurrenct_blit
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Makes one think if the original fix has been appropriate, when adding
> stop_machine for a software bug :P
I can reliably kill the machine with and without the patch in the same
manner. I don't believe I am seeing the same corruption that prompted
the w/a in the first place, so I've bitten the bullet and applied.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-02-23 9:33 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-20 12:47 [PATCH] drm/i915: Remove Braswell GGTT update w/a Chris Wilson
2017-02-20 13:52 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-02-22 11:27 ` [PATCH] " Joonas Lahtinen
2017-02-22 11:39 ` Chris Wilson
2017-02-22 18:02 ` Chris Wilson
2017-02-22 23:04 ` Chris Wilson
2017-02-23 9:33 ` Chris Wilson
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.