From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: Enable eLLC caching of display buffers for SKL+
Date: Mon, 15 Apr 2019 19:20:28 +0300 [thread overview]
Message-ID: <20190415162028.GB24299@intel.com> (raw)
In-Reply-To: <155534418936.22690.15673086288799437366@skylake-alporthouse-com>
On Mon, Apr 15, 2019 at 05:03:09PM +0100, Chris Wilson wrote:
> Quoting Patchwork (2019-04-15 16:21:30)
> > == Series Details ==
> >
> > Series: drm/i915: Enable eLLC caching of display buffers for SKL+
> > URL : https://patchwork.freedesktop.org/series/59502/
> > State : success
> >
> > == Summary ==
> >
> > CI Bug Log - changes from CI_DRM_5934 -> Patchwork_12799
> > ====================================================
> >
> > Summary
> > -------
> >
> > **SUCCESS**
> >
> > No regressions found.
>
> How good is our testing for detecting cacheline dirt from rendering?
>
> Now, it's pretty easy for us to test, you fire up a desktop and wiggle a
> few windows, but how well automated is it in CI?
Not well. Rendercopy sets MOCS to 0 which means UC, so it won't test
this at all. We should probably change that.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-15 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 14:16 [PATCH] drm/i915: Enable eLLC caching of display buffers for SKL+ Ville Syrjala
2019-04-15 15:02 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-04-15 15:03 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-04-15 15:21 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-15 16:03 ` Chris Wilson
2019-04-15 16:20 ` Ville Syrjälä [this message]
2019-04-15 17:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-04-16 14:28 ` [PATCH] " Eero Tamminen
2019-04-16 14:37 ` Ville Syrjälä
2019-04-17 7:09 ` Chris Wilson
2019-04-17 17:15 ` Ville Syrjälä
2019-04-26 14:54 ` Ville Syrjälä
2019-04-26 15:01 ` Chris Wilson
2019-04-26 15:13 ` Ville Syrjälä
2019-05-24 20:19 ` Chris Wilson
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=20190415162028.GB24299@intel.com \
--to=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox