On Thu, Oct 06, 2016 at 07:51:46AM +0100, Chris Wilson wrote:
> On Thu, Oct 06, 2016 at 09:31:32AM +0300, Petri Latvala wrote:
> > See tests/intel-ci/README for rationale and explanation.
>
> A lot of those tests are garbage and not future proof making them
> useless for regression testing.
On Thu, 06 Oct 2016, "Vivi, Rodrigo" wrote:
> On Tue, 2016-10-04 at 10:05 +0300, Jani Nikula wrote:
>> On Tue, 04 Oct 2016, "Vivi, Rodrigo" wrote:
>> > On Mon, 2016-10-03 at 13:50 +0300, Jani Nikula wrote:
>> >> On Fri, 30 Sep 2016, Rodrigo Vivi
On Thu, Oct 06, 2016 at 10:00:09AM +0300, Mika Kuoppala wrote:
> Hangcheck score has been zeroed on engine init, which happens
> after reset recovery. This has worked well as we always reset
> all engines on hang, and also discarded all work submitted
> to engines.
>
> With commit 821ed7df6e2a
On Thu, Oct 06, 2016 at 09:57:29AM +0300, Joonas Lahtinen wrote:
> On ke, 2016-10-05 at 21:05 +0100, Chris Wilson wrote:
> > In order not to trigger hangcheck on a idle-but-waiting engine, we need
> > to distinguish between the pending request queue and the actual
> > execution queue. This is done
On ke, 2016-10-05 at 17:53 +0100, Tvrtko Ursulin wrote:
> On 05/10/2016 17:50, Tvrtko Ursulin wrote:
> >
> >
> > On 05/10/2016 16:07, Joonas Lahtinen wrote:
> > >
> > > On ke, 2016-10-05 at 13:33 +0100, Tvrtko Ursulin wrote:
> > > >
> > > > From: Tvrtko Ursulin
> > >
On ke, 2016-10-05 at 21:05 +0100, Chris Wilson wrote:
> In order not to trigger hangcheck on a idle-but-waiting engine, we need
> to distinguish between the pending request queue and the actual
> execution queue. This is done later in "drm/i915: Enable multiple
> timelines" but for now we need a
On Wed, Oct 05, 2016 at 04:20:04PM -0700, Anusha Srivatsa wrote:
> Proper functioning of HuC requires GuC to be
> loaded. Make GuC loads default so that HuC works
> seemlessly.
> Also, note that GuC submission is not made default
> and still needs to be given as a kernel parameter.
> Once the
On Thu, Oct 06, 2016 at 09:31:32AM +0300, Petri Latvala wrote:
> See tests/intel-ci/README for rationale and explanation.
A lot of those tests are garbage and not future proof making them
useless for regression testing. Including them just adds noise and us
ignoring the results.
-Chris
--
Chris
See tests/intel-ci/README for rationale and explanation.
Signed-off-by: Petri Latvala
---
The plans for CI are to use explicit test lists in the future, as laid
out in this commit. Comments, acks, nacks, flames, etc would be very
welcome.
The only list so far is a
101 - 109 of 109 matches
Mail list logo