From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: warning for drm/i915: Track number of pending freed objects (rev2)
Date: Tue, 20 Feb 2018 09:12:34 +0000 [thread overview]
Message-ID: <151911795493.27265.5777924306612278767@mail.alporthouse.com> (raw)
In-Reply-To: <20180220014051.27569.45031@emeril.freedesktop.org>
Quoting Patchwork (2018-02-20 01:40:51)
> == Series Details ==
>
> Series: drm/i915: Track number of pending freed objects (rev2)
> URL : https://patchwork.freedesktop.org/series/38537/
> State : warning
>
> == Summary ==
>
> Test gem_eio:
> Subgroup in-flight:
> pass -> FAIL (shard-hsw) fdo#104676
> Test kms_mmap_write_crc:
> pass -> SKIP (shard-apl)
> Test kms_setmode:
> Subgroup basic:
> pass -> FAIL (shard-hsw) fdo#99912
> Test perf:
> Subgroup oa-exponents:
> pass -> FAIL (shard-apl) fdo#102254
Good news, the object leak detectors (which depend on the RCU flushing)
were stable so DROP_FREED still appears to be working.
Pushed to dinq, thanks for the review.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-02-20 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 16:19 [PATCH] drm/i915: Track number of pending freed objects Chris Wilson
2018-02-19 16:46 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-19 18:13 ` [PATCH] " Tvrtko Ursulin
2018-02-19 18:17 ` Chris Wilson
2018-02-19 21:31 ` ✗ Fi.CI.IGT: warning for " Patchwork
2018-02-19 21:44 ` [PATCH] " Chris Wilson
2018-02-19 22:06 ` [PATCH v2] " Chris Wilson
2018-02-19 22:43 ` ✓ Fi.CI.BAT: success for drm/i915: Track number of pending freed objects (rev2) Patchwork
2018-02-20 1:40 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-02-20 9:12 ` Chris Wilson [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=151911795493.27265.5777924306612278767@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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.